Fossil SCM

Another typo fix in the backup.md doc

wyoung 2020-10-05 13:55 trunk
Commit eb34dd52e2422f84ea675b726b3d19968a90c73244182efe878ea9a90b5fb108
1 file changed +1 -1
+1 -1
--- www/backup.md
+++ www/backup.md
@@ -47,11 +47,11 @@
4747
your local clone to be a precise match to the remote, it needs to track
4848
changes to the shun table as well.
4949
5050
5151
52
-## Universioned Artifacts
52
+## Unversioned Artifacts
5353
5454
Data in Fossil’s [unversioned artifacts table][uv] doesn’t sync down by
5555
default unless you specifically ask for it. Like local configuration
5656
data, it doesn’t get pulled as part of a normal `fossil sync`, but
5757
*unlike* the config data, you don’t get unversioned files as part of the
5858
--- www/backup.md
+++ www/backup.md
@@ -47,11 +47,11 @@
47 your local clone to be a precise match to the remote, it needs to track
48 changes to the shun table as well.
49
50
51
52 ## Universioned Artifacts
53
54 Data in Fossil’s [unversioned artifacts table][uv] doesn’t sync down by
55 default unless you specifically ask for it. Like local configuration
56 data, it doesn’t get pulled as part of a normal `fossil sync`, but
57 *unlike* the config data, you don’t get unversioned files as part of the
58
--- www/backup.md
+++ www/backup.md
@@ -47,11 +47,11 @@
47 your local clone to be a precise match to the remote, it needs to track
48 changes to the shun table as well.
49
50
51
52 ## Unversioned Artifacts
53
54 Data in Fossil’s [unversioned artifacts table][uv] doesn’t sync down by
55 default unless you specifically ask for it. Like local configuration
56 data, it doesn’t get pulled as part of a normal `fossil sync`, but
57 *unlike* the config data, you don’t get unversioned files as part of the
58

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button