36
37
38
39
40
41
42
43
44
45
46
47
48
49
|
between repositories in the same way as every other artifact. In fact,
the sync algorithm has no knowledge of the meaning of the artifacts it
is syncing. As far as the sync algorithm is concerned, all artifacts are
alike. After the sync has occurs, the individual repositories must
make sense of the meaning of the various artifacts for themselves.
<h2>Interpretation Of Ticket Change Artifacts</h2>
Every ticket change artifact contains (among other things)
* a timestamp,
* a ticket ID, and
* one or more name/value pairs.
|
>
>
>
|
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
|
between repositories in the same way as every other artifact. In fact,
the sync algorithm has no knowledge of the meaning of the artifacts it
is syncing. As far as the sync algorithm is concerned, all artifacts are
alike. After the sync has occurs, the individual repositories must
make sense of the meaning of the various artifacts for themselves.
<h2>Interpretation Of Ticket Change Artifacts</h2>
<i>Note: The following is implementation detail which can be safely ignored by
casual users of fossil.</i>
Every ticket change artifact contains (among other things)
* a timestamp,
* a ticket ID, and
* one or more name/value pairs.
|