Fossil SCM
Update another potentially misleading reference to wiki format in check-in comments.
Commit
0f6526cbfe16fbcdfca2fec9716bc67aede9764a81fab2203d7fae6da4f72e1a
Parent
d6de7f2e4273291…
1 file changed
+8
-4
+8
-4
| --- www/wikitheory.wiki | ||
| +++ www/wikitheory.wiki | ||
| @@ -61,14 +61,18 @@ | ||
| 61 | 61 | format is used, it is trivial to move a file from wiki to embedded documentation |
| 62 | 62 | or back again as the project evolves. |
| 63 | 63 | |
| 64 | 64 | <h2>Bug-reports and check-in comments and Forum messages</h2> |
| 65 | 65 | |
| 66 | -The comments on check-ins and the text in the descriptions of bug reports | |
| 67 | -both use wiki formatting. Exactly the same set of formatting rules apply. | |
| 68 | -There is never a need to learn one formatting language for documentation | |
| 69 | -and a different markup for bugs or for check-in comments. | |
| 66 | +The comments on check-ins, forum posts, and the text in the | |
| 67 | +descriptions of bug reports both use wiki formatting. Exactly the | |
| 68 | +same set of formatting rules apply. There is never a need to learn | |
| 69 | +one formatting language for documentation and a different markup for | |
| 70 | +bugs or for check-in comments. | |
| 71 | + | |
| 72 | +Minor caveat: check-in messages are currently limited to the | |
| 73 | +fossil-wiki format. | |
| 70 | 74 | |
| 71 | 75 | <h2 id="assocwiki">Auxiliary notes attached to check-ins or branches</h2> |
| 72 | 76 | |
| 73 | 77 | Stand-alone wiki pages with special names "branch/<i>BRANCHNAME</i>" |
| 74 | 78 | or "checkin/<i>HASH</i>" are associated with the corresponding |
| 75 | 79 |
| --- www/wikitheory.wiki | |
| +++ www/wikitheory.wiki | |
| @@ -61,14 +61,18 @@ | |
| 61 | format is used, it is trivial to move a file from wiki to embedded documentation |
| 62 | or back again as the project evolves. |
| 63 | |
| 64 | <h2>Bug-reports and check-in comments and Forum messages</h2> |
| 65 | |
| 66 | The comments on check-ins and the text in the descriptions of bug reports |
| 67 | both use wiki formatting. Exactly the same set of formatting rules apply. |
| 68 | There is never a need to learn one formatting language for documentation |
| 69 | and a different markup for bugs or for check-in comments. |
| 70 | |
| 71 | <h2 id="assocwiki">Auxiliary notes attached to check-ins or branches</h2> |
| 72 | |
| 73 | Stand-alone wiki pages with special names "branch/<i>BRANCHNAME</i>" |
| 74 | or "checkin/<i>HASH</i>" are associated with the corresponding |
| 75 |
| --- www/wikitheory.wiki | |
| +++ www/wikitheory.wiki | |
| @@ -61,14 +61,18 @@ | |
| 61 | format is used, it is trivial to move a file from wiki to embedded documentation |
| 62 | or back again as the project evolves. |
| 63 | |
| 64 | <h2>Bug-reports and check-in comments and Forum messages</h2> |
| 65 | |
| 66 | The comments on check-ins, forum posts, and the text in the |
| 67 | descriptions of bug reports both use wiki formatting. Exactly the |
| 68 | same set of formatting rules apply. There is never a need to learn |
| 69 | one formatting language for documentation and a different markup for |
| 70 | bugs or for check-in comments. |
| 71 | |
| 72 | Minor caveat: check-in messages are currently limited to the |
| 73 | fossil-wiki format. |
| 74 | |
| 75 | <h2 id="assocwiki">Auxiliary notes attached to check-ins or branches</h2> |
| 76 | |
| 77 | Stand-alone wiki pages with special names "branch/<i>BRANCHNAME</i>" |
| 78 | or "checkin/<i>HASH</i>" are associated with the corresponding |
| 79 |