Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | update documentation |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | merge-integrate |
| Files: | files | file ages | folders |
| SHA1: |
d10eee3a4b091bf3ab08273e7cde38e9 |
| User & Date: | jan.nijtmans 2013-08-16 14:36:05.804 |
Context
|
2013-08-16
| ||
| 14:36 | update documentation Closed-Leaf check-in: d10eee3a4b user: jan.nijtmans tags: merge-integrate | |
| 13:45 | Allow multiple T-cards with the same tags, provided they are for different uuid's which are in strict increasing order. check-in: f2ae58e393 user: jan.nijtmans tags: merge-integrate | |
Changes
Changes to www/fileformat.wiki.
| ︙ | ︙ | |||
209 210 211 212 213 214 215 | character (ASCII 0x0A), and the complete text of the file. Compute the MD5 checksum of the result. A manifest might contain one or more T-cards used to set [./branching.wiki#tags | tags or properties] on the check-in. The format of the T-card is the same as described in <i>Control Artifacts</i> section below, except that the | | | 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 | character (ASCII 0x0A), and the complete text of the file. Compute the MD5 checksum of the result. A manifest might contain one or more T-cards used to set [./branching.wiki#tags | tags or properties] on the check-in. The format of the T-card is the same as described in <i>Control Artifacts</i> section below, except that the second argument is the single character "<b>*</b>" instead of an artifact ID. The <b>*</b> in place of the artifact ID indicates that the tag or property applies to the current artifact. It is not possible to encode the current artifact ID as part of an artifact, since the act of inserting the artifact ID would change the artifact ID, hence a <b>*</b> is used to represent "self". T-cards are typically added to manifests in order to set the <b>branch</b> property and a symbolic name when the check-in is intended to start a new branch. |
| ︙ | ︙ | |||
283 284 285 286 287 288 289 | Control artifacts are used to assign properties to other artifacts within the repository. The basic format of a control artifact is the same as a manifest or cluster. A control artifact is a text file divided into cards by newline characters. Each card has a single-character card type followed by arguments. Spaces separate the card type and the arguments. No surplus whitespace is allowed. | | > | 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 | Control artifacts are used to assign properties to other artifacts within the repository. The basic format of a control artifact is the same as a manifest or cluster. A control artifact is a text file divided into cards by newline characters. Each card has a single-character card type followed by arguments. Spaces separate the card type and the arguments. No surplus whitespace is allowed. All cards must occur in strict lexicographical order, but for T-cards the artifact-id sorts before the tag-name. Allowed cards in a control artifact are as follows: <blockquote> <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 /> |
| ︙ | ︙ |