Fossil SCM
Fixed a Markdown formatting problem due to a line break in an unfortunate location.
Commit
8e3898ac039d54dc016e80ad8d3ca9d51d910b2fc0c64d1b1d0ace3de0210370
Parent
fa4c48bf60e6de1…
1 file changed
+3
-3
+3
-3
| --- www/caps/admin-v-setup.md | ||
| +++ www/caps/admin-v-setup.md | ||
| @@ -394,13 +394,13 @@ | ||
| 394 | 394 | deliberately, hopefully after careful consideration. |
| 395 | 395 | |
| 396 | 396 | |
| 397 | 397 | ### <a name="y"></a>Write Unversioned |
| 398 | 398 | |
| 399 | -Fossil currently doesn’t distinguish the sub-operations of [`fossil | |
| 400 | -uv`](/help?cmd=uv); they’re all covered by [**WrUnver**][capy] (“y”) | |
| 401 | -capability. Since some of these operations are unconditionally | |
| 399 | +Fossil currently doesn’t distinguish the sub-operations of | |
| 400 | +[`fossil uv`](/help?cmd=uv); they’re all covered by [**WrUnver**][capy] | |
| 401 | +(“y”) 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 | 405 | Setup or Admin user must grant cap “y” to someone — not necessarily |
| 406 | 406 | themselves! — before modifications to remote |
| 407 | 407 |
| --- www/caps/admin-v-setup.md | |
| +++ www/caps/admin-v-setup.md | |
| @@ -394,13 +394,13 @@ | |
| 394 | deliberately, hopefully after careful consideration. |
| 395 | |
| 396 | |
| 397 | ### <a name="y"></a>Write Unversioned |
| 398 | |
| 399 | Fossil currently doesn’t distinguish the sub-operations of [`fossil |
| 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 |
| --- www/caps/admin-v-setup.md | |
| +++ www/caps/admin-v-setup.md | |
| @@ -394,13 +394,13 @@ | |
| 394 | deliberately, hopefully after careful consideration. |
| 395 | |
| 396 | |
| 397 | ### <a name="y"></a>Write Unversioned |
| 398 | |
| 399 | Fossil currently doesn’t distinguish the sub-operations of |
| 400 | [`fossil uv`](/help?cmd=uv); they’re all covered by [**WrUnver**][capy] |
| 401 | (“y”) 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 |