Fossil SCM
Added a paragraph to the unvers doc on the "y" capability.
Commit
faffd271927ee6e2c211a97b69cd30083a3cd180b40bceb3c9f03dd053f45ea1
Parent
d1a3dda6a7c9d2c…
1 file changed
+9
+9
| --- www/unvers.wiki | ||
| +++ www/unvers.wiki | ||
| @@ -55,10 +55,19 @@ | ||
| 55 | 55 | [/help?cmd=unversioned|fossil unversioned revert] command. The |
| 56 | 56 | "unversioned revert" |
| 57 | 57 | command causes the unversioned content on the local repository to overwritten |
| 58 | 58 | by the unversioned content found on the remote repository. |
| 59 | 59 | |
| 60 | +Beware that because unversioned file sync is an uncommonly dangerous | |
| 61 | +capability — there being no history to revert to in the case of human | |
| 62 | +error — even the all-powerful Fossil "setup" user does not get | |
| 63 | +unversioned file sync capability by default. See | |
| 64 | +[./caps/admin-v-setup.md#dcap | this] for the full details, but the | |
| 65 | +short-and-sweet takeaway is that a user needs the "y" capability on the | |
| 66 | +remote before they can sync unversioned content. Until then, you're | |
| 67 | +allowed to add such files to your local repo, but they will not sync. | |
| 68 | + | |
| 60 | 69 | <h2>Implementation Details</h2> |
| 61 | 70 | |
| 62 | 71 | <i>(This section outlines the current implementation of unversioned |
| 63 | 72 | files. This is not an interface spec and hence subject to change.)</i> |
| 64 | 73 | |
| 65 | 74 |
| --- www/unvers.wiki | |
| +++ www/unvers.wiki | |
| @@ -55,10 +55,19 @@ | |
| 55 | [/help?cmd=unversioned|fossil unversioned revert] command. The |
| 56 | "unversioned revert" |
| 57 | command causes the unversioned content on the local repository to overwritten |
| 58 | by the unversioned content found on the remote repository. |
| 59 | |
| 60 | <h2>Implementation Details</h2> |
| 61 | |
| 62 | <i>(This section outlines the current implementation of unversioned |
| 63 | files. This is not an interface spec and hence subject to change.)</i> |
| 64 | |
| 65 |
| --- www/unvers.wiki | |
| +++ www/unvers.wiki | |
| @@ -55,10 +55,19 @@ | |
| 55 | [/help?cmd=unversioned|fossil unversioned revert] command. The |
| 56 | "unversioned revert" |
| 57 | command causes the unversioned content on the local repository to overwritten |
| 58 | by the unversioned content found on the remote repository. |
| 59 | |
| 60 | Beware that because unversioned file sync is an uncommonly dangerous |
| 61 | capability — there being no history to revert to in the case of human |
| 62 | error — even the all-powerful Fossil "setup" user does not get |
| 63 | unversioned file sync capability by default. See |
| 64 | [./caps/admin-v-setup.md#dcap | this] for the full details, but the |
| 65 | short-and-sweet takeaway is that a user needs the "y" capability on the |
| 66 | remote before they can sync unversioned content. Until then, you're |
| 67 | allowed to add such files to your local repo, but they will not sync. |
| 68 | |
| 69 | <h2>Implementation Details</h2> |
| 70 | |
| 71 | <i>(This section outlines the current implementation of unversioned |
| 72 | files. This is not an interface spec and hence subject to change.)</i> |
| 73 | |
| 74 |