Fossil SCM
Fix a doc typo. Minor improvements to documentation linkage.
Commit
c468769dbca5199f57f432c6e517b330b591e986
Parent
1438be02d02f27e…
3 files changed
+5
+1
-1
+3
-2
+5
| --- www/concepts.wiki | ||
| +++ www/concepts.wiki | ||
| @@ -13,10 +13,15 @@ | ||
| 13 | 13 | to setup and operate. |
| 14 | 14 | |
| 15 | 15 | This document is intended as a quick introduction to the concepts |
| 16 | 16 | behind Fossil. |
| 17 | 17 | |
| 18 | +See also: | |
| 19 | + | |
| 20 | + * [./whyusefossil.wiki#definitions|Definitions] | |
| 21 | + * [./quickstart.wiki|Quick start guide] | |
| 22 | + | |
| 18 | 23 | <h2>2.0 Composition Of A Project</h2> |
| 19 | 24 | <img src="concept1.gif" align="right" hspace="10"> |
| 20 | 25 | |
| 21 | 26 | A software project normally consists of a "source tree". |
| 22 | 27 | A source tree is a hierarchy of files that are used to generate |
| 23 | 28 |
| --- www/concepts.wiki | |
| +++ www/concepts.wiki | |
| @@ -13,10 +13,15 @@ | |
| 13 | to setup and operate. |
| 14 | |
| 15 | This document is intended as a quick introduction to the concepts |
| 16 | behind Fossil. |
| 17 | |
| 18 | <h2>2.0 Composition Of A Project</h2> |
| 19 | <img src="concept1.gif" align="right" hspace="10"> |
| 20 | |
| 21 | A software project normally consists of a "source tree". |
| 22 | A source tree is a hierarchy of files that are used to generate |
| 23 |
| --- www/concepts.wiki | |
| +++ www/concepts.wiki | |
| @@ -13,10 +13,15 @@ | |
| 13 | to setup and operate. |
| 14 | |
| 15 | This document is intended as a quick introduction to the concepts |
| 16 | behind Fossil. |
| 17 | |
| 18 | See also: |
| 19 | |
| 20 | * [./whyusefossil.wiki#definitions|Definitions] |
| 21 | * [./quickstart.wiki|Quick start guide] |
| 22 | |
| 23 | <h2>2.0 Composition Of A Project</h2> |
| 24 | <img src="concept1.gif" align="right" hspace="10"> |
| 25 | |
| 26 | A software project normally consists of a "source tree". |
| 27 | A source tree is a hierarchy of files that are used to generate |
| 28 |
+1
-1
| --- www/server.wiki | ||
| +++ www/server.wiki | ||
| @@ -39,11 +39,11 @@ | ||
| 39 | 39 | access these using URLs of the form <b>http://localhost:8080/</b>, or if |
| 40 | 40 | <i>REPOSITORY</i> is a directory, URLs of the form |
| 41 | 41 | <b>http://localhost:8080/</b><i>repo</i><b>/</b> where <i>repo</i> is the base |
| 42 | 42 | name of the repository file without the ".fossil" suffix. |
| 43 | 43 | The difference between "ui" and "server" is that "ui" will |
| 44 | -also start a web browser and points it | |
| 44 | +also start a web browser and point it | |
| 45 | 45 | to the URL mentioned above, and the "ui" command binds to |
| 46 | 46 | the loopback IP address (127.0.0.1) only so that the "ui" command cannot be |
| 47 | 47 | used to serve content to a different machine. |
| 48 | 48 | </p> |
| 49 | 49 | <p> |
| 50 | 50 |
| --- www/server.wiki | |
| +++ www/server.wiki | |
| @@ -39,11 +39,11 @@ | |
| 39 | access these using URLs of the form <b>http://localhost:8080/</b>, or if |
| 40 | <i>REPOSITORY</i> is a directory, URLs of the form |
| 41 | <b>http://localhost:8080/</b><i>repo</i><b>/</b> where <i>repo</i> is the base |
| 42 | name of the repository file without the ".fossil" suffix. |
| 43 | The difference between "ui" and "server" is that "ui" will |
| 44 | also start a web browser and points it |
| 45 | to the URL mentioned above, and the "ui" command binds to |
| 46 | the loopback IP address (127.0.0.1) only so that the "ui" command cannot be |
| 47 | used to serve content to a different machine. |
| 48 | </p> |
| 49 | <p> |
| 50 |
| --- www/server.wiki | |
| +++ www/server.wiki | |
| @@ -39,11 +39,11 @@ | |
| 39 | access these using URLs of the form <b>http://localhost:8080/</b>, or if |
| 40 | <i>REPOSITORY</i> is a directory, URLs of the form |
| 41 | <b>http://localhost:8080/</b><i>repo</i><b>/</b> where <i>repo</i> is the base |
| 42 | name of the repository file without the ".fossil" suffix. |
| 43 | The difference between "ui" and "server" is that "ui" will |
| 44 | also start a web browser and point it |
| 45 | to the URL mentioned above, and the "ui" command binds to |
| 46 | the loopback IP address (127.0.0.1) only so that the "ui" command cannot be |
| 47 | used to serve content to a different machine. |
| 48 | </p> |
| 49 | <p> |
| 50 |
+3
-2
| --- www/whyusefossil.wiki | ||
| +++ www/whyusefossil.wiki | ||
| @@ -37,10 +37,11 @@ | ||
| 37 | 37 | <li>Failed disk-drives cause no loss of work |
| 38 | 38 | <li>Avoid wasting time doing manual file copying |
| 39 | 39 | <li>Avoid human errors during manual backups |
| 40 | 40 | </ol> |
| 41 | 41 | </ol> |
| 42 | +<a name='definitions'></a> | |
| 42 | 43 | <li><p><b>Definitions</b></p> |
| 43 | 44 | <ul> |
| 44 | 45 | <li><p><b>Project</b> → |
| 45 | 46 | a collection of computer files that serve some common |
| 46 | 47 | purpose. Often the project is a software application and the |
| @@ -59,12 +60,12 @@ | ||
| 59 | 60 | project that has files scattered hither and yon all over |
| 60 | 61 | the disk. In other words, Fossil only works for projects |
| 61 | 62 | where the files are laid out such that they can be archived |
| 62 | 63 | into a ZIP file or tarball. |
| 63 | 64 | </ul> |
| 64 | - <li><p><b>Repository</b> | |
| 65 | - (also called "repo") → a single file that contains | |
| 65 | + <li><p><b>Repository</b> → | |
| 66 | + (also called "repo") a single file that contains | |
| 66 | 67 | all historical versions of all files in a project. A repo is similar |
| 67 | 68 | to a ZIP archive in that it is a single file that stores compressed |
| 68 | 69 | versions of many other files. Files can be extracted from the |
| 69 | 70 | repo and new files can be added to the repo, just as with a ZIP |
| 70 | 71 | archive. But a repo has other capabilities above and beyond |
| 71 | 72 |
| --- www/whyusefossil.wiki | |
| +++ www/whyusefossil.wiki | |
| @@ -37,10 +37,11 @@ | |
| 37 | <li>Failed disk-drives cause no loss of work |
| 38 | <li>Avoid wasting time doing manual file copying |
| 39 | <li>Avoid human errors during manual backups |
| 40 | </ol> |
| 41 | </ol> |
| 42 | <li><p><b>Definitions</b></p> |
| 43 | <ul> |
| 44 | <li><p><b>Project</b> → |
| 45 | a collection of computer files that serve some common |
| 46 | purpose. Often the project is a software application and the |
| @@ -59,12 +60,12 @@ | |
| 59 | project that has files scattered hither and yon all over |
| 60 | the disk. In other words, Fossil only works for projects |
| 61 | where the files are laid out such that they can be archived |
| 62 | into a ZIP file or tarball. |
| 63 | </ul> |
| 64 | <li><p><b>Repository</b> |
| 65 | (also called "repo") → a single file that contains |
| 66 | all historical versions of all files in a project. A repo is similar |
| 67 | to a ZIP archive in that it is a single file that stores compressed |
| 68 | versions of many other files. Files can be extracted from the |
| 69 | repo and new files can be added to the repo, just as with a ZIP |
| 70 | archive. But a repo has other capabilities above and beyond |
| 71 |
| --- www/whyusefossil.wiki | |
| +++ www/whyusefossil.wiki | |
| @@ -37,10 +37,11 @@ | |
| 37 | <li>Failed disk-drives cause no loss of work |
| 38 | <li>Avoid wasting time doing manual file copying |
| 39 | <li>Avoid human errors during manual backups |
| 40 | </ol> |
| 41 | </ol> |
| 42 | <a name='definitions'></a> |
| 43 | <li><p><b>Definitions</b></p> |
| 44 | <ul> |
| 45 | <li><p><b>Project</b> → |
| 46 | a collection of computer files that serve some common |
| 47 | purpose. Often the project is a software application and the |
| @@ -59,12 +60,12 @@ | |
| 60 | project that has files scattered hither and yon all over |
| 61 | the disk. In other words, Fossil only works for projects |
| 62 | where the files are laid out such that they can be archived |
| 63 | into a ZIP file or tarball. |
| 64 | </ul> |
| 65 | <li><p><b>Repository</b> → |
| 66 | (also called "repo") a single file that contains |
| 67 | all historical versions of all files in a project. A repo is similar |
| 68 | to a ZIP archive in that it is a single file that stores compressed |
| 69 | versions of many other files. Files can be extracted from the |
| 70 | repo and new files can be added to the repo, just as with a ZIP |
| 71 | archive. But a repo has other capabilities above and beyond |
| 72 |