Fossil SCM
Fix a few typos in documentation.
Commit
4ef19b554a19b7423f8cd3f30e23db1099efba30
Parent
d0e8e88d546eda1…
3 files changed
+3
-3
+6
-7
+1
-1
+3
-3
| --- src/wiki.c | ||
| +++ src/wiki.c | ||
| @@ -528,18 +528,18 @@ | ||
| 528 | 528 | @ <li> <p><b>Paragraphs</b>. Any sequence of one or more blank lines forms |
| 529 | 529 | @ a paragraph break. Centered or right-justified paragraphs are not |
| 530 | 530 | @ supported by wiki markup, but you can do these things if you need them |
| 531 | 531 | @ using HTML.</p> |
| 532 | 532 | @ <li> <p><b>Bullet Lists</b>. |
| 533 | - @ A bullet list item are lines that begin with a single "*" character | |
| 533 | + @ A bullet list item is a line that begins with a single "*" character | |
| 534 | 534 | @ surrounded on |
| 535 | 535 | @ both sides by two or more spaces or by a tab. Only a single level |
| 536 | 536 | @ of bullet list is supported by wiki. For nested lists, use HTML.</p> |
| 537 | 537 | @ <li> <p><b>Enumeration Lists</b>. |
| 538 | - @ An enumeration list items are lines that begin | |
| 538 | + @ An enumeration list item is a line that begins | |
| 539 | 539 | @ with one or more digits optionally |
| 540 | - @ followed by a "." and surrounded on both sides by two or more spaces or | |
| 540 | + @ followed by a "." and is surrounded on both sides by two or more spaces or | |
| 541 | 541 | @ by a tab. The number is significant and becomes the number shown |
| 542 | 542 | @ in the rendered enumeration item. Only a single level of enumeration |
| 543 | 543 | @ list is supported by wiki. For nested enumerations or for |
| 544 | 544 | @ enumerations that count using letters or roman numerials, use HTML.</p> |
| 545 | 545 | @ <li> <p><b>Indented Paragraphs</b>. |
| 546 | 546 |
| --- src/wiki.c | |
| +++ src/wiki.c | |
| @@ -528,18 +528,18 @@ | |
| 528 | @ <li> <p><b>Paragraphs</b>. Any sequence of one or more blank lines forms |
| 529 | @ a paragraph break. Centered or right-justified paragraphs are not |
| 530 | @ supported by wiki markup, but you can do these things if you need them |
| 531 | @ using HTML.</p> |
| 532 | @ <li> <p><b>Bullet Lists</b>. |
| 533 | @ A bullet list item are lines that begin with a single "*" character |
| 534 | @ surrounded on |
| 535 | @ both sides by two or more spaces or by a tab. Only a single level |
| 536 | @ of bullet list is supported by wiki. For nested lists, use HTML.</p> |
| 537 | @ <li> <p><b>Enumeration Lists</b>. |
| 538 | @ An enumeration list items are lines that begin |
| 539 | @ with one or more digits optionally |
| 540 | @ followed by a "." and surrounded on both sides by two or more spaces or |
| 541 | @ by a tab. The number is significant and becomes the number shown |
| 542 | @ in the rendered enumeration item. Only a single level of enumeration |
| 543 | @ list is supported by wiki. For nested enumerations or for |
| 544 | @ enumerations that count using letters or roman numerials, use HTML.</p> |
| 545 | @ <li> <p><b>Indented Paragraphs</b>. |
| 546 |
| --- src/wiki.c | |
| +++ src/wiki.c | |
| @@ -528,18 +528,18 @@ | |
| 528 | @ <li> <p><b>Paragraphs</b>. Any sequence of one or more blank lines forms |
| 529 | @ a paragraph break. Centered or right-justified paragraphs are not |
| 530 | @ supported by wiki markup, but you can do these things if you need them |
| 531 | @ using HTML.</p> |
| 532 | @ <li> <p><b>Bullet Lists</b>. |
| 533 | @ A bullet list item is a line that begins with a single "*" character |
| 534 | @ surrounded on |
| 535 | @ both sides by two or more spaces or by a tab. Only a single level |
| 536 | @ of bullet list is supported by wiki. For nested lists, use HTML.</p> |
| 537 | @ <li> <p><b>Enumeration Lists</b>. |
| 538 | @ An enumeration list item is a line that begins |
| 539 | @ with one or more digits optionally |
| 540 | @ followed by a "." and is surrounded on both sides by two or more spaces or |
| 541 | @ by a tab. The number is significant and becomes the number shown |
| 542 | @ in the rendered enumeration item. Only a single level of enumeration |
| 543 | @ list is supported by wiki. For nested enumerations or for |
| 544 | @ enumerations that count using letters or roman numerials, use HTML.</p> |
| 545 | @ <li> <p><b>Indented Paragraphs</b>. |
| 546 |
+6
-7
| --- www/qandc.wiki | ||
| +++ www/qandc.wiki | ||
| @@ -62,18 +62,18 @@ | ||
| 62 | 62 | |
| 63 | 63 | <b>Fossil looks like the bug tracker that would be in your |
| 64 | 64 | Linksys Router's administration screen.</p> |
| 65 | 65 | |
| 66 | 66 | <blockquote> |
| 67 | -<p>I take a pragmatic approach to software: form follows functions. | |
| 68 | -To me, it is more important to have a highly reliable, fast, efficient, | |
| 67 | +<p>I take a pragmatic approach to software: form follows function. | |
| 68 | +To me, it is more important to have a reliable, fast, efficient, | |
| 69 | 69 | enduring, and simple DVCS than one that looks pretty.</p> |
| 70 | 70 | |
| 71 | 71 | <p>On the other hand, if you have patches that improve the apparance |
| 72 | 72 | of Fossil without seriously compromising its reliablity, performance, |
| 73 | -an maintainability, I will be happy to accept them. Fossil is | |
| 74 | -self-hosting. Send me email to request a password that will let | |
| 73 | +and/or maintainability, I will be happy to accept them. Fossil is | |
| 74 | +self-hosting. Send email to request a password that will let | |
| 75 | 75 | you push to the main fossil repository.</p> |
| 76 | 76 | </blockquote> |
| 77 | 77 | |
| 78 | 78 | <b>It would be useful to have a separate application that |
| 79 | 79 | keeps the bug-tracking database in a versioned file. That file can |
| @@ -99,12 +99,11 @@ | ||
| 99 | 99 | <blockquote> |
| 100 | 100 | The use of SQLite to store the database is likely more stable and secure |
| 101 | 101 | than any other approach, due to the fact that SQLite is transactional. |
| 102 | 102 | Fossil also implements several internal |
| 103 | 103 | <a href="selfcheck.wiki">self-checks</a> to insure that no information |
| 104 | -is ever lost. And, indeed, in over a year of operation, there have been | |
| 105 | -no reports of data loss due to a Fossil malfunction. | |
| 104 | +is ever lost. | |
| 106 | 105 | </blockquote> |
| 107 | 106 | |
| 108 | 107 | |
| 109 | 108 | <b>I am dubious of the benefits of including wikis and bug trackers |
| 110 | 109 | directly in the VCS - either they are under-featured compared to full |
| @@ -112,11 +111,11 @@ | ||
| 112 | 111 | Subversion or Bazaar.</b> |
| 113 | 112 | |
| 114 | 113 | <blockquote> |
| 115 | 114 | <p>I have no doubt that Trac has many features that fossil lacks. But that |
| 116 | 115 | is not the point. Fossil has several key features that Trac lacks and that |
| 117 | -I cannot live without: most notably the fact that | |
| 116 | +I need: most notably the fact that | |
| 118 | 117 | fossil supports disconnected operation.</p> |
| 119 | 118 | |
| 120 | 119 | <p>As for bloat: Fossil is a single self-contained executable. |
| 121 | 120 | You do not need any other packages |
| 122 | 121 | (diff, patch, merge, cvs, svn, rcs, git, python, perl, tcl, apache, |
| 123 | 122 |
| --- www/qandc.wiki | |
| +++ www/qandc.wiki | |
| @@ -62,18 +62,18 @@ | |
| 62 | |
| 63 | <b>Fossil looks like the bug tracker that would be in your |
| 64 | Linksys Router's administration screen.</p> |
| 65 | |
| 66 | <blockquote> |
| 67 | <p>I take a pragmatic approach to software: form follows functions. |
| 68 | To me, it is more important to have a highly reliable, fast, efficient, |
| 69 | enduring, and simple DVCS than one that looks pretty.</p> |
| 70 | |
| 71 | <p>On the other hand, if you have patches that improve the apparance |
| 72 | of Fossil without seriously compromising its reliablity, performance, |
| 73 | an maintainability, I will be happy to accept them. Fossil is |
| 74 | self-hosting. Send me email to request a password that will let |
| 75 | you push to the main fossil repository.</p> |
| 76 | </blockquote> |
| 77 | |
| 78 | <b>It would be useful to have a separate application that |
| 79 | keeps the bug-tracking database in a versioned file. That file can |
| @@ -99,12 +99,11 @@ | |
| 99 | <blockquote> |
| 100 | The use of SQLite to store the database is likely more stable and secure |
| 101 | than any other approach, due to the fact that SQLite is transactional. |
| 102 | Fossil also implements several internal |
| 103 | <a href="selfcheck.wiki">self-checks</a> to insure that no information |
| 104 | is ever lost. And, indeed, in over a year of operation, there have been |
| 105 | no reports of data loss due to a Fossil malfunction. |
| 106 | </blockquote> |
| 107 | |
| 108 | |
| 109 | <b>I am dubious of the benefits of including wikis and bug trackers |
| 110 | directly in the VCS - either they are under-featured compared to full |
| @@ -112,11 +111,11 @@ | |
| 112 | Subversion or Bazaar.</b> |
| 113 | |
| 114 | <blockquote> |
| 115 | <p>I have no doubt that Trac has many features that fossil lacks. But that |
| 116 | is not the point. Fossil has several key features that Trac lacks and that |
| 117 | I cannot live without: most notably the fact that |
| 118 | fossil supports disconnected operation.</p> |
| 119 | |
| 120 | <p>As for bloat: Fossil is a single self-contained executable. |
| 121 | You do not need any other packages |
| 122 | (diff, patch, merge, cvs, svn, rcs, git, python, perl, tcl, apache, |
| 123 |
| --- www/qandc.wiki | |
| +++ www/qandc.wiki | |
| @@ -62,18 +62,18 @@ | |
| 62 | |
| 63 | <b>Fossil looks like the bug tracker that would be in your |
| 64 | Linksys Router's administration screen.</p> |
| 65 | |
| 66 | <blockquote> |
| 67 | <p>I take a pragmatic approach to software: form follows function. |
| 68 | To me, it is more important to have a reliable, fast, efficient, |
| 69 | enduring, and simple DVCS than one that looks pretty.</p> |
| 70 | |
| 71 | <p>On the other hand, if you have patches that improve the apparance |
| 72 | of Fossil without seriously compromising its reliablity, performance, |
| 73 | and/or maintainability, I will be happy to accept them. Fossil is |
| 74 | self-hosting. Send email to request a password that will let |
| 75 | you push to the main fossil repository.</p> |
| 76 | </blockquote> |
| 77 | |
| 78 | <b>It would be useful to have a separate application that |
| 79 | keeps the bug-tracking database in a versioned file. That file can |
| @@ -99,12 +99,11 @@ | |
| 99 | <blockquote> |
| 100 | The use of SQLite to store the database is likely more stable and secure |
| 101 | than any other approach, due to the fact that SQLite is transactional. |
| 102 | Fossil also implements several internal |
| 103 | <a href="selfcheck.wiki">self-checks</a> to insure that no information |
| 104 | is ever lost. |
| 105 | </blockquote> |
| 106 | |
| 107 | |
| 108 | <b>I am dubious of the benefits of including wikis and bug trackers |
| 109 | directly in the VCS - either they are under-featured compared to full |
| @@ -112,11 +111,11 @@ | |
| 111 | Subversion or Bazaar.</b> |
| 112 | |
| 113 | <blockquote> |
| 114 | <p>I have no doubt that Trac has many features that fossil lacks. But that |
| 115 | is not the point. Fossil has several key features that Trac lacks and that |
| 116 | I need: most notably the fact that |
| 117 | fossil supports disconnected operation.</p> |
| 118 | |
| 119 | <p>As for bloat: Fossil is a single self-contained executable. |
| 120 | You do not need any other packages |
| 121 | (diff, patch, merge, cvs, svn, rcs, git, python, perl, tcl, apache, |
| 122 |
+1
-1
| --- www/wikitheory.wiki | ||
| +++ www/wikitheory.wiki | ||
| @@ -20,11 +20,11 @@ | ||
| 20 | 20 | Each wiki page has its own revision history which is independent of |
| 21 | 21 | the sequence of baselines (check-ins). Wiki pages can branch and merge |
| 22 | 22 | just like baselines, though as of this writing (2008-07-29) there is |
| 23 | 23 | no mechanism in the user interface to support branching and merging. |
| 24 | 24 | The current implementation of the wiki shows the version of the wiki |
| 25 | -pages that has the most recent timestamp. | |
| 25 | +page that has the most recent timestamp. | |
| 26 | 26 | |
| 27 | 27 | In other words, if two users make unrelated changes to the same wiki |
| 28 | 28 | page on separate repositories, then those repositories are synced, |
| 29 | 29 | the wiki page will fork. The web interface will display whichever edit |
| 30 | 30 | was checked in last. The other edit can be found in the history. The |
| 31 | 31 |
| --- www/wikitheory.wiki | |
| +++ www/wikitheory.wiki | |
| @@ -20,11 +20,11 @@ | |
| 20 | Each wiki page has its own revision history which is independent of |
| 21 | the sequence of baselines (check-ins). Wiki pages can branch and merge |
| 22 | just like baselines, though as of this writing (2008-07-29) there is |
| 23 | no mechanism in the user interface to support branching and merging. |
| 24 | The current implementation of the wiki shows the version of the wiki |
| 25 | pages that has the most recent timestamp. |
| 26 | |
| 27 | In other words, if two users make unrelated changes to the same wiki |
| 28 | page on separate repositories, then those repositories are synced, |
| 29 | the wiki page will fork. The web interface will display whichever edit |
| 30 | was checked in last. The other edit can be found in the history. The |
| 31 |
| --- www/wikitheory.wiki | |
| +++ www/wikitheory.wiki | |
| @@ -20,11 +20,11 @@ | |
| 20 | Each wiki page has its own revision history which is independent of |
| 21 | the sequence of baselines (check-ins). Wiki pages can branch and merge |
| 22 | just like baselines, though as of this writing (2008-07-29) there is |
| 23 | no mechanism in the user interface to support branching and merging. |
| 24 | The current implementation of the wiki shows the version of the wiki |
| 25 | page that has the most recent timestamp. |
| 26 | |
| 27 | In other words, if two users make unrelated changes to the same wiki |
| 28 | page on separate repositories, then those repositories are synced, |
| 29 | the wiki page will fork. The web interface will display whichever edit |
| 30 | was checked in last. The other edit can be found in the history. The |
| 31 |