Fossil SCM
fileformat.wiki tweaks for attachments support.
Commit
c4ba59b73e27fdc3fe5c158d8c047c305b2e545669c8c5340dc02952398c0fdc
Parent
363649c5799b3af…
1 file changed
+5
-6
+5
-6
| --- www/fileformat.wiki | ||
| +++ www/fileformat.wiki | ||
| @@ -424,14 +424,13 @@ | ||
| 424 | 424 | [/artifact/91f1ec6af053 | here]. |
| 425 | 425 | |
| 426 | 426 | <h3 id="attachment">2.6 Attachments</h3> |
| 427 | 427 | |
| 428 | 428 | An attachment artifact associates some other artifact that is the |
| 429 | -attachment (the source artifact) with a ticket or wiki page or | |
| 430 | -technical note to which | |
| 431 | -the attachment is connected (the target artifact). | |
| 432 | -The following cards are allowed on an attachment artifact: | |
| 429 | +attachment (the source artifact) with a ticket, wiki page, technical | |
| 430 | +note, or forum post to which the attachment is connected (the target | |
| 431 | +artifact). The following cards are allowed on an attachment artifact: | |
| 433 | 432 | |
| 434 | 433 | <div class="indent"> |
| 435 | 434 | <b>A</b> <i>filename target</i> ?<i>source</i>?<br /> |
| 436 | 435 | <b>C</b> <i>comment</i><br /> |
| 437 | 436 | <b>D</b> <i>time-and-date-stamp</i><br /> |
| @@ -446,11 +445,11 @@ | ||
| 446 | 445 | which the attachment is connected. The third argument is either |
| 447 | 446 | missing or else it is the lower-case artifact ID of the attachment |
| 448 | 447 | itself. A missing third argument means that the attachment should be |
| 449 | 448 | deleted. If <i>source</i> is a forum post, the hash provided should |
| 450 | 449 | generally be the hash of the first version of the post for reasons |
| 451 | -[#forumpost-tag|explained in the section on tags]. | |
| 450 | +[#forumpost-tag|explained elsewhere]. | |
| 452 | 451 | |
| 453 | 452 | The <b>C</b> card is an optional comment describing what the attachment is about. |
| 454 | 453 | The <b>C</b> card is optional, but there can only be one. |
| 455 | 454 | |
| 456 | 455 | A single <b>D</b> card is required to give the date and time when the attachment |
| @@ -611,11 +610,11 @@ | ||
| 611 | 610 | <h4>2.8.1 Tags and Attachments on Forum Posts</h4> |
| 612 | 611 | |
| 613 | 612 | When adding [#ctrl|tags] or [#attachment|attachments] to [#forum|forum |
| 614 | 613 | posts] it is generally up to the application to tag, or attach to, |
| 615 | 614 | only the first version of any given post. For example, if post X has |
| 616 | -two edits, a tag or applied, or attachment added, by the user to post | |
| 615 | +two edits then a tag applied, or attachment added, by the user to post | |
| 617 | 616 | X+2 should generally be applied to version X instead. Though this |
| 618 | 617 | complicates the app logic for applying tags, it simplifies the app's |
| 619 | 618 | location of tags for purposes of applying tag-/attachment-dependent |
| 620 | 619 | logic. As of this writing (May 2026), no current Fossil use cases |
| 621 | 620 | would be improved by tagging specific subsequent versions of posts, |
| 622 | 621 |
| --- www/fileformat.wiki | |
| +++ www/fileformat.wiki | |
| @@ -424,14 +424,13 @@ | |
| 424 | [/artifact/91f1ec6af053 | here]. |
| 425 | |
| 426 | <h3 id="attachment">2.6 Attachments</h3> |
| 427 | |
| 428 | An attachment artifact associates some other artifact that is the |
| 429 | attachment (the source artifact) with a ticket or wiki page or |
| 430 | technical note to which |
| 431 | the attachment is connected (the target artifact). |
| 432 | The following cards are allowed on an attachment artifact: |
| 433 | |
| 434 | <div class="indent"> |
| 435 | <b>A</b> <i>filename target</i> ?<i>source</i>?<br /> |
| 436 | <b>C</b> <i>comment</i><br /> |
| 437 | <b>D</b> <i>time-and-date-stamp</i><br /> |
| @@ -446,11 +445,11 @@ | |
| 446 | which the attachment is connected. The third argument is either |
| 447 | missing or else it is the lower-case artifact ID of the attachment |
| 448 | itself. A missing third argument means that the attachment should be |
| 449 | deleted. If <i>source</i> is a forum post, the hash provided should |
| 450 | generally be the hash of the first version of the post for reasons |
| 451 | [#forumpost-tag|explained in the section on tags]. |
| 452 | |
| 453 | The <b>C</b> card is an optional comment describing what the attachment is about. |
| 454 | The <b>C</b> card is optional, but there can only be one. |
| 455 | |
| 456 | A single <b>D</b> card is required to give the date and time when the attachment |
| @@ -611,11 +610,11 @@ | |
| 611 | <h4>2.8.1 Tags and Attachments on Forum Posts</h4> |
| 612 | |
| 613 | When adding [#ctrl|tags] or [#attachment|attachments] to [#forum|forum |
| 614 | posts] it is generally up to the application to tag, or attach to, |
| 615 | only the first version of any given post. For example, if post X has |
| 616 | two edits, a tag or applied, or attachment added, by the user to post |
| 617 | X+2 should generally be applied to version X instead. Though this |
| 618 | complicates the app logic for applying tags, it simplifies the app's |
| 619 | location of tags for purposes of applying tag-/attachment-dependent |
| 620 | logic. As of this writing (May 2026), no current Fossil use cases |
| 621 | would be improved by tagging specific subsequent versions of posts, |
| 622 |
| --- www/fileformat.wiki | |
| +++ www/fileformat.wiki | |
| @@ -424,14 +424,13 @@ | |
| 424 | [/artifact/91f1ec6af053 | here]. |
| 425 | |
| 426 | <h3 id="attachment">2.6 Attachments</h3> |
| 427 | |
| 428 | An attachment artifact associates some other artifact that is the |
| 429 | attachment (the source artifact) with a ticket, wiki page, technical |
| 430 | note, or forum post to which the attachment is connected (the target |
| 431 | artifact). The following cards are allowed on an attachment artifact: |
| 432 | |
| 433 | <div class="indent"> |
| 434 | <b>A</b> <i>filename target</i> ?<i>source</i>?<br /> |
| 435 | <b>C</b> <i>comment</i><br /> |
| 436 | <b>D</b> <i>time-and-date-stamp</i><br /> |
| @@ -446,11 +445,11 @@ | |
| 445 | which the attachment is connected. The third argument is either |
| 446 | missing or else it is the lower-case artifact ID of the attachment |
| 447 | itself. A missing third argument means that the attachment should be |
| 448 | deleted. If <i>source</i> is a forum post, the hash provided should |
| 449 | generally be the hash of the first version of the post for reasons |
| 450 | [#forumpost-tag|explained elsewhere]. |
| 451 | |
| 452 | The <b>C</b> card is an optional comment describing what the attachment is about. |
| 453 | The <b>C</b> card is optional, but there can only be one. |
| 454 | |
| 455 | A single <b>D</b> card is required to give the date and time when the attachment |
| @@ -611,11 +610,11 @@ | |
| 610 | <h4>2.8.1 Tags and Attachments on Forum Posts</h4> |
| 611 | |
| 612 | When adding [#ctrl|tags] or [#attachment|attachments] to [#forum|forum |
| 613 | posts] it is generally up to the application to tag, or attach to, |
| 614 | only the first version of any given post. For example, if post X has |
| 615 | two edits then a tag applied, or attachment added, by the user to post |
| 616 | X+2 should generally be applied to version X instead. Though this |
| 617 | complicates the app logic for applying tags, it simplifies the app's |
| 618 | location of tags for purposes of applying tag-/attachment-dependent |
| 619 | logic. As of this writing (May 2026), no current Fossil use cases |
| 620 | would be improved by tagging specific subsequent versions of posts, |
| 621 |