Fossil SCM
Merged another redundant page title in the whyusefossil doc. Also, making use of the new h5 level formatting to avoid the need for inline manual boldfacing.
Commit
b1a709a1a4edba785575040e27be3a0e82877a1d816f234c90728c195517ec11
Parent
4003c654b660a9d…
1 file changed
+11
-11
+11
-11
| --- www/whyusefossil.wiki | ||
| +++ www/whyusefossil.wiki | ||
| @@ -1,12 +1,12 @@ | ||
| 1 | -<title>Why Use Fossil</title> | |
| 2 | -<h1 align='center'>Why You Should Use Fossil</h1> | |
| 3 | -<p align='center'><b>Or, if not Fossil, at least some kind of modern | |
| 4 | -version control<br>such as Git, Mercurial, or Subversion.</b></p> | |
| 5 | -<p align='center'>(Presented in outline form, for people in a hurry)</p> | |
| 1 | +<title>Why You Should Use Fossil</title> | |
| 2 | + | |
| 3 | +<h4>(Or if not Fossil, at least some kind of modern | |
| 4 | +version control such as Git, Mercurial, or Subversion.)</h4> | |
| 6 | 5 | |
| 7 | -<b>I. Benefits of Version Control</b> | |
| 6 | +<h5>I. Benefits of Version Control</h5> | |
| 7 | + | |
| 8 | 8 | <ol type='A'> |
| 9 | 9 | <li><p><b>Immutable file and version identification</b> |
| 10 | 10 | <ol type='i'> |
| 11 | 11 | <li>Simplified and unambiguous communication between developers |
| 12 | 12 | <li>Detect accidental or surreptitious changes |
| @@ -37,15 +37,15 @@ | ||
| 37 | 37 | <li>Avoid wasting time doing manual file copying |
| 38 | 38 | <li>Avoid human errors during manual backups |
| 39 | 39 | </ol> |
| 40 | 40 | </ol> |
| 41 | 41 | |
| 42 | -<p id="definitions"><b>II. Definitions</b></p> | |
| 42 | +<h5 id="definitions">II. Definitions</h5> | |
| 43 | 43 | |
| 44 | -Moved to [./glossary.md | a separate document]. | |
| 44 | +<div class="indent">Moved to [./glossary.md | a separate document].</div> | |
| 45 | 45 | |
| 46 | -<p><b>III. Basic Fossil commands</b> | |
| 46 | +<h5>III. Basic Fossil commands</h5> | |
| 47 | 47 | |
| 48 | 48 | <ul> |
| 49 | 49 | <li><p><b>clone</b> → |
| 50 | 50 | Make a copy of a repository. The original repository |
| 51 | 51 | is usually (but not always) on a remote machine and the copy is on |
| @@ -87,11 +87,11 @@ | ||
| 87 | 87 | in that they specify pending changes to the structure of the check-out. |
| 88 | 88 | As with "add", no changes are made to the repository until the next |
| 89 | 89 | "commit". |
| 90 | 90 | </ul> |
| 91 | 91 | |
| 92 | -<b>IV. The history of a project is a Directed Acyclic Graph (DAG)</b> | |
| 92 | +<h5>IV. The history of a project is a Directed Acyclic Graph (DAG)</h5> | |
| 93 | 93 | |
| 94 | 94 | <ul> |
| 95 | 95 | <li><p>Fossil (and other distributed VCSes like Git and Mercurial, but |
| 96 | 96 | not Subversion) represent |
| 97 | 97 | the history of a project as a directed acyclic graph (DAG). |
| @@ -142,11 +142,11 @@ | ||
| 142 | 142 | to the first check-in of a branch. The name assigned by this |
| 143 | 143 | special tag automatically propagates to all direct children. |
| 144 | 144 | </ul> |
| 145 | 145 | </ul> |
| 146 | 146 | |
| 147 | -<b>V. Why version control is important (reprise)</b> | |
| 147 | +<h5>V. Why version control is important (reprise)</h5> | |
| 148 | 148 | |
| 149 | 149 | <ol> |
| 150 | 150 | <li><p>Every check-in and every individual file has a unique name - its |
| 151 | 151 | SHA1 or SHA3-256 hash. Team members can unambiguously identify |
| 152 | 152 | any specific |
| 153 | 153 |
| --- www/whyusefossil.wiki | |
| +++ www/whyusefossil.wiki | |
| @@ -1,12 +1,12 @@ | |
| 1 | <title>Why Use Fossil</title> |
| 2 | <h1 align='center'>Why You Should Use Fossil</h1> |
| 3 | <p align='center'><b>Or, if not Fossil, at least some kind of modern |
| 4 | version control<br>such as Git, Mercurial, or Subversion.</b></p> |
| 5 | <p align='center'>(Presented in outline form, for people in a hurry)</p> |
| 6 | |
| 7 | <b>I. Benefits of Version Control</b> |
| 8 | <ol type='A'> |
| 9 | <li><p><b>Immutable file and version identification</b> |
| 10 | <ol type='i'> |
| 11 | <li>Simplified and unambiguous communication between developers |
| 12 | <li>Detect accidental or surreptitious changes |
| @@ -37,15 +37,15 @@ | |
| 37 | <li>Avoid wasting time doing manual file copying |
| 38 | <li>Avoid human errors during manual backups |
| 39 | </ol> |
| 40 | </ol> |
| 41 | |
| 42 | <p id="definitions"><b>II. Definitions</b></p> |
| 43 | |
| 44 | Moved to [./glossary.md | a separate document]. |
| 45 | |
| 46 | <p><b>III. Basic Fossil commands</b> |
| 47 | |
| 48 | <ul> |
| 49 | <li><p><b>clone</b> → |
| 50 | Make a copy of a repository. The original repository |
| 51 | is usually (but not always) on a remote machine and the copy is on |
| @@ -87,11 +87,11 @@ | |
| 87 | in that they specify pending changes to the structure of the check-out. |
| 88 | As with "add", no changes are made to the repository until the next |
| 89 | "commit". |
| 90 | </ul> |
| 91 | |
| 92 | <b>IV. The history of a project is a Directed Acyclic Graph (DAG)</b> |
| 93 | |
| 94 | <ul> |
| 95 | <li><p>Fossil (and other distributed VCSes like Git and Mercurial, but |
| 96 | not Subversion) represent |
| 97 | the history of a project as a directed acyclic graph (DAG). |
| @@ -142,11 +142,11 @@ | |
| 142 | to the first check-in of a branch. The name assigned by this |
| 143 | special tag automatically propagates to all direct children. |
| 144 | </ul> |
| 145 | </ul> |
| 146 | |
| 147 | <b>V. Why version control is important (reprise)</b> |
| 148 | |
| 149 | <ol> |
| 150 | <li><p>Every check-in and every individual file has a unique name - its |
| 151 | SHA1 or SHA3-256 hash. Team members can unambiguously identify |
| 152 | any specific |
| 153 |
| --- www/whyusefossil.wiki | |
| +++ www/whyusefossil.wiki | |
| @@ -1,12 +1,12 @@ | |
| 1 | <title>Why You Should Use Fossil</title> |
| 2 | |
| 3 | <h4>(Or if not Fossil, at least some kind of modern |
| 4 | version control such as Git, Mercurial, or Subversion.)</h4> |
| 5 | |
| 6 | <h5>I. Benefits of Version Control</h5> |
| 7 | |
| 8 | <ol type='A'> |
| 9 | <li><p><b>Immutable file and version identification</b> |
| 10 | <ol type='i'> |
| 11 | <li>Simplified and unambiguous communication between developers |
| 12 | <li>Detect accidental or surreptitious changes |
| @@ -37,15 +37,15 @@ | |
| 37 | <li>Avoid wasting time doing manual file copying |
| 38 | <li>Avoid human errors during manual backups |
| 39 | </ol> |
| 40 | </ol> |
| 41 | |
| 42 | <h5 id="definitions">II. Definitions</h5> |
| 43 | |
| 44 | <div class="indent">Moved to [./glossary.md | a separate document].</div> |
| 45 | |
| 46 | <h5>III. Basic Fossil commands</h5> |
| 47 | |
| 48 | <ul> |
| 49 | <li><p><b>clone</b> → |
| 50 | Make a copy of a repository. The original repository |
| 51 | is usually (but not always) on a remote machine and the copy is on |
| @@ -87,11 +87,11 @@ | |
| 87 | in that they specify pending changes to the structure of the check-out. |
| 88 | As with "add", no changes are made to the repository until the next |
| 89 | "commit". |
| 90 | </ul> |
| 91 | |
| 92 | <h5>IV. The history of a project is a Directed Acyclic Graph (DAG)</h5> |
| 93 | |
| 94 | <ul> |
| 95 | <li><p>Fossil (and other distributed VCSes like Git and Mercurial, but |
| 96 | not Subversion) represent |
| 97 | the history of a project as a directed acyclic graph (DAG). |
| @@ -142,11 +142,11 @@ | |
| 142 | to the first check-in of a branch. The name assigned by this |
| 143 | special tag automatically propagates to all direct children. |
| 144 | </ul> |
| 145 | </ul> |
| 146 | |
| 147 | <h5>V. Why version control is important (reprise)</h5> |
| 148 | |
| 149 | <ol> |
| 150 | <li><p>Every check-in and every individual file has a unique name - its |
| 151 | SHA1 or SHA3-256 hash. Team members can unambiguously identify |
| 152 | any specific |
| 153 |