Fossil SCM
Small tweaks to previous.
Commit
1ff41ddaea182cfeca642e9ef8dbadad1717ee1c8a90be7ec656ecb888f0826f
Parent
8a77f4593e52c51…
1 file changed
+3
-3
+3
-3
| --- www/caps/admin-v-setup.md | ||
| +++ www/caps/admin-v-setup.md | ||
| @@ -252,11 +252,11 @@ | ||
| 252 | 252 | |
| 253 | 253 | ## <a name="apsu"></a>The All-Powerful Setup User |
| 254 | 254 | |
| 255 | 255 | Setup users get [every user capability](./ref.html) of Fossil except for |
| 256 | 256 | [two exceptionally dangerous capabilities](#dcap), which they can later |
| 257 | -grant to themselves or to others at the Setup user’s discretion. | |
| 257 | +grant to themselves or to others. | |
| 258 | 258 | |
| 259 | 259 | In addition, Setup users can use every feature of the Fossil UI. If Fossil can do a |
| 260 | 260 | thing, a Setup user on that repo can make Fossil do it. |
| 261 | 261 | |
| 262 | 262 | Setup users can do many things that Admin users cannot: |
| @@ -400,12 +400,12 @@ | ||
| 400 | 400 | uv`](/help?cmd=uv); they’re all covered by [**WrUnver**][capy] (“y”) |
| 401 | 401 | capability. Since some of these operations are unconditionally |
| 402 | 402 | destructive due to the nature of unversioned content, and since this |
| 403 | 403 | goes against Fossil’s philosophy of immutable history, nobody gets cap |
| 404 | 404 | “y” on a Fossil repo by default, not even the Setup or Admin users. A |
| 405 | -Setup or Admin user must grant “y” cap to someone — not necessarily | |
| 406 | -themselves! — this powerful capability before modifications to remote | |
| 405 | +Setup or Admin user must grant cap “y” to someone — not necessarily | |
| 406 | +themselves! — before modifications to remote | |
| 407 | 407 | unversioned content are possible. |
| 408 | 408 | |
| 409 | 409 | Operations on unversioned content made without this capability affect |
| 410 | 410 | your local clone only. In this way, your local unversioned file table |
| 411 | 411 | can have different content from that in its parent repo. This state of |
| 412 | 412 |
| --- www/caps/admin-v-setup.md | |
| +++ www/caps/admin-v-setup.md | |
| @@ -252,11 +252,11 @@ | |
| 252 | |
| 253 | ## <a name="apsu"></a>The All-Powerful Setup User |
| 254 | |
| 255 | Setup users get [every user capability](./ref.html) of Fossil except for |
| 256 | [two exceptionally dangerous capabilities](#dcap), which they can later |
| 257 | grant to themselves or to others at the Setup user’s discretion. |
| 258 | |
| 259 | In addition, Setup users can use every feature of the Fossil UI. If Fossil can do a |
| 260 | thing, a Setup user on that repo can make Fossil do it. |
| 261 | |
| 262 | Setup users can do many things that Admin users cannot: |
| @@ -400,12 +400,12 @@ | |
| 400 | uv`](/help?cmd=uv); they’re all covered by [**WrUnver**][capy] (“y”) |
| 401 | capability. Since some of these operations are unconditionally |
| 402 | destructive due to the nature of unversioned content, and since this |
| 403 | goes against Fossil’s philosophy of immutable history, nobody gets cap |
| 404 | “y” on a Fossil repo by default, not even the Setup or Admin users. A |
| 405 | Setup or Admin user must grant “y” cap to someone — not necessarily |
| 406 | themselves! — this powerful capability before modifications to remote |
| 407 | unversioned content are possible. |
| 408 | |
| 409 | Operations on unversioned content made without this capability affect |
| 410 | your local clone only. In this way, your local unversioned file table |
| 411 | can have different content from that in its parent repo. This state of |
| 412 |
| --- www/caps/admin-v-setup.md | |
| +++ www/caps/admin-v-setup.md | |
| @@ -252,11 +252,11 @@ | |
| 252 | |
| 253 | ## <a name="apsu"></a>The All-Powerful Setup User |
| 254 | |
| 255 | Setup users get [every user capability](./ref.html) of Fossil except for |
| 256 | [two exceptionally dangerous capabilities](#dcap), which they can later |
| 257 | grant to themselves or to others. |
| 258 | |
| 259 | In addition, Setup users can use every feature of the Fossil UI. If Fossil can do a |
| 260 | thing, a Setup user on that repo can make Fossil do it. |
| 261 | |
| 262 | Setup users can do many things that Admin users cannot: |
| @@ -400,12 +400,12 @@ | |
| 400 | uv`](/help?cmd=uv); they’re all covered by [**WrUnver**][capy] (“y”) |
| 401 | capability. Since some of these operations are unconditionally |
| 402 | destructive due to the nature of unversioned content, and since this |
| 403 | goes against Fossil’s philosophy of immutable history, nobody gets cap |
| 404 | “y” on a Fossil repo by default, not even the Setup or Admin users. A |
| 405 | Setup or Admin user must grant cap “y” to someone — not necessarily |
| 406 | themselves! — before modifications to remote |
| 407 | unversioned content are possible. |
| 408 | |
| 409 | Operations on unversioned content made without this capability affect |
| 410 | your local clone only. In this way, your local unversioned file table |
| 411 | can have different content from that in its parent repo. This state of |
| 412 |