59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
|
repository.
Fossil recognizes the following kinds of structural
artifacts:
<ul>
<li> [#manifest | Manifests] </li>
<li> [#cluster | Clusters] </li>
<li> [#ctrl | Control Artifacts] </li>
<li> [#wikichng | Wiki Pages] </li>
<li> [#tktchng | Ticket Changes] </li>
<li> [#attachment | Attachments] </li>
<li> [#event | TechNotes] </li>
<li> [#forum | Forum Posts] </li>
</ul>
|
|
|
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
|
repository.
Fossil recognizes the following kinds of structural
artifacts:
<ul>
<li> [#manifest | Manifests] </li>
<li> [#cluster | Clusters] </li>
<li> [#ctrl | Control (a.k.a. Tag) Artifacts] </li>
<li> [#wikichng | Wiki Pages] </li>
<li> [#tktchng | Ticket Changes] </li>
<li> [#attachment | Attachments] </li>
<li> [#event | TechNotes] </li>
<li> [#forum | Forum Posts] </li>
</ul>
|
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
|
the <b>Z</b> card of a manifest. The argument to the <b>Z</b> card is the
lower-case hexadecimal representation of the MD5 checksum of all
prior cards in the cluster. The <b>Z</b> card is required.
An example cluster from Fossil can be seen
[/artifact/d03dbdd73a2a8 | here].
<h3 id="ctrl">2.3 Control Artifacts</h3>
Control artifacts are used to assign properties to other artifacts
within the repository.
Allowed cards in a control artifact are as follows:
<div class="indent">
<b>D</b> <i>time-and-date-stamp</i><br />
<b>T</b> (<b>+</b>|<b>-</b>|<b>*</b>)<i>tag-name</i> <i>artifact-id</i> ?<i>value</i>?<br />
<b>U</b> <i>user-name</i><br />
<b>Z</b> <i>checksum</i><br />
</div>
A control artifact must have one <b>D</b> card, one <b>U</b> card, one <b>Z</b> card and
one or more <b>T</b> cards. No other cards or other text is
allowed in a control artifact. Control artifacts might be PGP
clearsigned.
The <b>D</b> card and the <b>Z</b> card of a control artifact are the same
|
|
|
|
>
>
>
>
|
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
|
the <b>Z</b> card of a manifest. The argument to the <b>Z</b> card is the
lower-case hexadecimal representation of the MD5 checksum of all
prior cards in the cluster. The <b>Z</b> card is required.
An example cluster from Fossil can be seen
[/artifact/d03dbdd73a2a8 | here].
<h3 id="ctrl">2.3 Control (a.k.a. Tag) Artifacts</h3>
Control artifacts are used to assign properties to other artifacts
within the repository. Allowed cards in a control artifact are as
follows:
<div class="indent">
<b>D</b> <i>time-and-date-stamp</i><br />
<b>T</b> (<b>+</b>|<b>-</b>|<b>*</b>)<i>tag-name</i> <i>artifact-id</i> ?<i>value</i>?<br />
<b>U</b> <i>user-name</i><br />
<b>Z</b> <i>checksum</i><br />
</div>
Control articles are also referred to as Tag artifacts, but tags can
also be applied via other artifact types, as described in
[#summary|the Card Summary table].
A control artifact must have one <b>D</b> card, one <b>U</b> card, one <b>Z</b> card and
one or more <b>T</b> cards. No other cards or other text is
allowed in a control artifact. Control artifacts might be PGP
clearsigned.
The <b>D</b> card and the <b>Z</b> card of a control artifact are the same
|