1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
|
<title>Unversioned Content</title>
<h1 align="center">Unversioned Content</h1>
"Unversioned content" or "unversioned files" are
files stored in a Fossil repository without history, meaning
it retains the newest version of each such file, and that alone.
Though it omits history, Fossil does sync unversioned content between
repositories. In the event of a conflict during a sync, it retains
the most recent version of each unversioned file, discrding
older versions.
Unversioned files are useful for storing ephemeral content such as builds
or frequently changing web pages. We store
the [https://fossil-scm.org/home/uv/download.html|download] page of
the self-hosting Fossil repository as unversioned
content, for example.
|
|
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
|
<title>Unversioned Content</title>
<h1 align="center">Unversioned Content</h1>
"Unversioned content" or "unversioned files" are
files stored in a Fossil repository without history, meaning
it retains the newest version of each such file, and that alone.
Though it omits history, Fossil does sync unversioned content between
repositories. In the event of a conflict during a sync, it retains
the most recent version of each unversioned file, discarding
older versions.
Unversioned files are useful for storing ephemeral content such as builds
or frequently changing web pages. We store
the [https://fossil-scm.org/home/uv/download.html|download] page of
the self-hosting Fossil repository as unversioned
content, for example.
|
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
|
</pre></blockquote>
Lacking history for unversioned files, Fossil does not attempt delta
compression on them.
Fossil servers exchange unversioned content whole; it does not attempt
to "diff" your local version against the remote and send only the
changes. We point tihs out because one use-case for unversioned content
is to send large, frequently-changing files. Appreciate the consequences
before making each change.
There are two bandwidth-saving measures in "<tt>fossil uv sync</tt>".
The first is the regular HTTP payload compression step, done on all
syncs. The second is that Fossil sends SHA1 hash exchanges to determine
when it can avoid sending duplicate content over the wire unnecessarily.
See the [./sync.wiki|synchronization protocol documentation] for further
information.
|
|
|
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
|
</pre></blockquote>
Lacking history for unversioned files, Fossil does not attempt delta
compression on them.
Fossil servers exchange unversioned content whole; it does not attempt
to "diff" your local version against the remote and send only the
changes. We point this out because one use-case for unversioned content
is to send large, frequently-changing files. Appreciate the consequences
before making each change.
There are two bandwidth-saving measures in "<tt>fossil uv sync</tt>".
The first is the regular HTTP payload compression step, done on all
syncs. The second is that Fossil sends SHA1 hash exchanges to determine
when it can avoid sending duplicate content over the wire unnecessarily.
See the [./sync.wiki|synchronization protocol documentation] for further
information.
|