| ︙ | | | ︙ | |
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
|
</p>
<p>
Allowed cards in the cluster are as follows:
</p>
<blockquote>
<b>M</b> <i>uuid</i><br />
<b>Z</b> <i>checksum</i>
</blockquote>
<p>
A cluster contains one or more "M" cards followed by a single "Z"
line. Each M card has a single argument which is the UUID of
another artifact in the repository. The Z card work exactly like
the Z card of a manifest. The argument to the Z card is the
lower-case hexadecimal representation of the MD5 checksum of all
prior cards in the cluster. Note that the Z card is required
on a cluster.
</p>
|
|
|
|
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
|
</p>
<p>
Allowed cards in the cluster are as follows:
</p>
<blockquote>
<b>M</b> <i>artifact-id</i><br />
<b>Z</b> <i>checksum</i>
</blockquote>
<p>
A cluster contains one or more "M" cards followed by a single "Z"
line. Each M card has a single argument which is the artifact ID of
another artifact in the repository. The Z card work exactly like
the Z card of a manifest. The argument to the Z card is the
lower-case hexadecimal representation of the MD5 checksum of all
prior cards in the cluster. Note that the Z card is required
on a cluster.
</p>
|
| ︙ | | | ︙ | |
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
|
<p>
Allowed cards in a control artifact are as follows:
</p>
<blockquote>
<b>D</b> <i>time-and-date-stamp</i><br />
<b>T</b> (<b>+</b>|<b>-</b>|<b>*</b>)<i>tag-name uuid ?value?</i><br />
<b>Z</b> <i>checksum</i><br />
</blockquote>
<p>
A control artifact must have one D card and one Z card and
one or more or more T cards. No other cards or other text is
allowed in a control artifact. Control artifacts might be PGP
clearsigned.</p>
<p>The D card and the Z card of a control artifact are the same
as in a manifest.</p>
<p>The T card represents a "tag" or property that is applied to
some other artifact. The T card has two or three values. The
second argument is the 40 character lowercase UUID of the artifact
to which the tag is to be applied. The
first value is the tag name. The first character of the tag
is either "+", "-", or "*". A "+" means the tag should be added
to the artifact. The "-" means the tag should be removed.
The "*" character means the tag should be added to the artifact
and all direct decendants (but not branches) of the artifact down
to but not including the first decendant that contains a
|
|
|
|
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
|
<p>
Allowed cards in a control artifact are as follows:
</p>
<blockquote>
<b>D</b> <i>time-and-date-stamp</i><br />
<b>T</b> (<b>+</b>|<b>-</b>|<b>*</b>)<i>tag-name artifact-id ?value?</i><br />
<b>Z</b> <i>checksum</i><br />
</blockquote>
<p>
A control artifact must have one D card and one Z card and
one or more or more T cards. No other cards or other text is
allowed in a control artifact. Control artifacts might be PGP
clearsigned.</p>
<p>The D card and the Z card of a control artifact are the same
as in a manifest.</p>
<p>The T card represents a "tag" or property that is applied to
some other artifact. The T card has two or three values. The
second argument is the 40 character lowercase artifact ID of the artifact
to which the tag is to be applied. The
first value is the tag name. The first character of the tag
is either "+", "-", or "*". A "+" means the tag should be added
to the artifact. The "-" means the tag should be removed.
The "*" character means the tag should be added to the artifact
and all direct decendants (but not branches) of the artifact down
to but not including the first decendant that contains a
|
| ︙ | | | ︙ | |
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
|
cards by newline characters. The format of each card is as in
manifests, clusters, and control artifacts. Wiki artifacts accept
the following card types:</p>
<blockquote>
<b>D</b> <i>time-and-date-stamp</i><br />
<b>L</b> <i>wiki-title</i><br />
<b>P</b> <i>parent-uuid</i>+<br />
<b>U</b> <i>user-name</i><br />
<b>W</b> <i>size</i> <b>\n</b> <i>text</i> <b>\n</b><br />
<b>Z</b> <i>checksum</i>
</blockquote>
<p>The D card is the date and time when the wiki page was edited.
The P card specifies the parent wiki pages, if any. The L card
|
|
|
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
|
cards by newline characters. The format of each card is as in
manifests, clusters, and control artifacts. Wiki artifacts accept
the following card types:</p>
<blockquote>
<b>D</b> <i>time-and-date-stamp</i><br />
<b>L</b> <i>wiki-title</i><br />
<b>P</b> <i>parent-artifact-id</i>+<br />
<b>U</b> <i>user-name</i><br />
<b>W</b> <i>size</i> <b>\n</b> <i>text</i> <b>\n</b><br />
<b>Z</b> <i>checksum</i>
</blockquote>
<p>The D card is the date and time when the wiki page was edited.
The P card specifies the parent wiki pages, if any. The L card
|
| ︙ | | | ︙ | |
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
|
<p>A ticket-change artifact represents a change to a trouble ticket.
The following cards are allowed on a ticket change artifact:</p>
<blockquote>
<b>D</b> <i>time-and-date-stamp</i><br />
<b>J</b> ?<b>+</b>?<i>name value</i><br />
<b>K</b> <i>ticket-uuid</i><br />
<b>U</b> <i>user-name</i><br />
<b>Z</b> <i>checksum</i>
</blockquote>
<p>
The D card is the usual date and time stamp and represents the point
in time when the change was entered. The U card is the login of the
programmer who entered this change. The Z card is the checksum over
the entire artifact.</p>
<p>
Every ticket has a UUID. The ticket to which this change is applied
is specified by the K card. A ticket exists if it contains one or
more changes. The first "change" to a ticket is what brings the
ticket into existance.</p>
<p>
J cards specify changes to "fields" of the ticket. Each fossil
server has a ticket configuration which specifies the fields its
|
|
|
|
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
|
<p>A ticket-change artifact represents a change to a trouble ticket.
The following cards are allowed on a ticket change artifact:</p>
<blockquote>
<b>D</b> <i>time-and-date-stamp</i><br />
<b>J</b> ?<b>+</b>?<i>name value</i><br />
<b>K</b> <i>ticket-id</i><br />
<b>U</b> <i>user-name</i><br />
<b>Z</b> <i>checksum</i>
</blockquote>
<p>
The D card is the usual date and time stamp and represents the point
in time when the change was entered. The U card is the login of the
programmer who entered this change. The Z card is the checksum over
the entire artifact.</p>
<p>
Every ticket has a unique ID. The ticket to which this change is applied
is specified by the K card. A ticket exists if it contains one or
more changes. The first "change" to a ticket is what brings the
ticket into existance.</p>
<p>
J cards specify changes to "fields" of the ticket. Each fossil
server has a ticket configuration which specifies the fields its
|
| ︙ | | | ︙ | |