Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | typo's |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
882f7a5dad1cc58018eacc47f762cbe8 |
| User & Date: | jan.nijtmans 2013-08-23 10:07:54.289 |
Context
|
2013-08-23
| ||
| 13:15 | Report "E-card in ???" syntax errors as "?-card in event". Refactoring needed for next commit. No change in functionality. check-in: 6324a3ce6b user: jan.nijtmans tags: trunk | |
| 10:07 | typo's check-in: 882f7a5dad user: jan.nijtmans tags: trunk | |
| 09:54 | According to the documentation [/artifact/9974dfbc5c?txt=1&ln=178-179], the first manifest in the project has no P-card. Make it so, as a P-card with no arguments is just ignored and serves no purpose. (I tested this in a new repo, and it works just fine) check-in: 989c99351e user: jan.nijtmans tags: trunk | |
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. |
| ︙ | ︙ | |||
506 507 508 509 510 511 512 | that it might be space efficient to store one event as a delta of the other. An event might contain one or more T-cards used to set [./branching.wiki#tags | tags or properties] on the event. The format of the T-card is the same as described in [#ctrl | Control Artifacts] section above, except that the | | | 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 | that it might be space efficient to store one event as a delta of the other. An event might contain one or more T-cards used to set [./branching.wiki#tags | tags or properties] on the event. The format of the T-card is the same as described in [#ctrl | Control Artifacts] section above, except that the second argument is the single character "<b>*</b>" instead of an artifact ID and the name is always prefaced by "<b>+</b>". 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". The "<b>+</b>" on the name means that tags can only be add and they can only be non-propagating |
| ︙ | ︙ |