Fossil SCM
A few clarifications to the new glossary.
Commit
78aa43940719f3c065f23ffd76ce134b89e36fc43e6287e0e850cd2bb993a31a
Parent
65dbf97eb8a6e70…
1 file changed
+7
-5
+7
-5
| --- www/glossary.md | ||
| +++ www/glossary.md | ||
| @@ -101,20 +101,22 @@ | ||
| 101 | 101 | |
| 102 | 102 | A single file that contains all historical versions of all files in a |
| 103 | 103 | project, which can be [cloned] to other machines and |
| 104 | 104 | [synchronized][sync] with them. Jargon: repo. |
| 105 | 105 | |
| 106 | -* A Fossil repo is similar to a zip archive in that it is a single | |
| 106 | +* A Fossil repo is similar to an archive file in that it is a single | |
| 107 | 107 | file that stores compressed versions of one or more files. Files can be |
| 108 | 108 | extracted from the repo, and new files can be added to the repo, |
| 109 | - just as with a zip archive, but a Fossil repo has other capabilities | |
| 109 | + but a Fossil repo has other capabilities | |
| 110 | 110 | above and beyond what simple archive formats can do. |
| 111 | 111 | |
| 112 | 112 | * Fossil does not care what you name your repository files, though |
| 113 | - we do suggest appending “`.fossil` as a standard extension. There is | |
| 114 | - only one place in Fossil where that’s required, being the “directory | |
| 115 | - name” form of [the `fossil server DIRECTORY` command][svrcmd]. | |
| 113 | + we do suggest “`.fossil`” as a standard extension. There is | |
| 114 | + only one place in Fossil where that convention is required, being the | |
| 115 | + [`fossil server DIRECTORY`][svrcmd] command, since it serves up | |
| 116 | + `*.fossil` files from `DIRECTORY`. If you don’t use that feature, | |
| 117 | + you can name your repo files anything you like. | |
| 116 | 118 | |
| 117 | 119 | * Cloned and synced repos redundantly store all available information |
| 118 | 120 | about that project, so if any one repo is lost, all of the cloned |
| 119 | 121 | historical content of the project as of the last sync is preserved |
| 120 | 122 | in each surviving repo. |
| 121 | 123 |
| --- www/glossary.md | |
| +++ www/glossary.md | |
| @@ -101,20 +101,22 @@ | |
| 101 | |
| 102 | A single file that contains all historical versions of all files in a |
| 103 | project, which can be [cloned] to other machines and |
| 104 | [synchronized][sync] with them. Jargon: repo. |
| 105 | |
| 106 | * A Fossil repo is similar to a zip archive in that it is a single |
| 107 | file that stores compressed versions of one or more files. Files can be |
| 108 | extracted from the repo, and new files can be added to the repo, |
| 109 | just as with a zip archive, but a Fossil repo has other capabilities |
| 110 | above and beyond what simple archive formats can do. |
| 111 | |
| 112 | * Fossil does not care what you name your repository files, though |
| 113 | we do suggest appending “`.fossil` as a standard extension. There is |
| 114 | only one place in Fossil where that’s required, being the “directory |
| 115 | name” form of [the `fossil server DIRECTORY` command][svrcmd]. |
| 116 | |
| 117 | * Cloned and synced repos redundantly store all available information |
| 118 | about that project, so if any one repo is lost, all of the cloned |
| 119 | historical content of the project as of the last sync is preserved |
| 120 | in each surviving repo. |
| 121 |
| --- www/glossary.md | |
| +++ www/glossary.md | |
| @@ -101,20 +101,22 @@ | |
| 101 | |
| 102 | A single file that contains all historical versions of all files in a |
| 103 | project, which can be [cloned] to other machines and |
| 104 | [synchronized][sync] with them. Jargon: repo. |
| 105 | |
| 106 | * A Fossil repo is similar to an archive file in that it is a single |
| 107 | file that stores compressed versions of one or more files. Files can be |
| 108 | extracted from the repo, and new files can be added to the repo, |
| 109 | but a Fossil repo has other capabilities |
| 110 | above and beyond what simple archive formats can do. |
| 111 | |
| 112 | * Fossil does not care what you name your repository files, though |
| 113 | we do suggest “`.fossil`” as a standard extension. There is |
| 114 | only one place in Fossil where that convention is required, being the |
| 115 | [`fossil server DIRECTORY`][svrcmd] command, since it serves up |
| 116 | `*.fossil` files from `DIRECTORY`. If you don’t use that feature, |
| 117 | you can name your repo files anything you like. |
| 118 | |
| 119 | * Cloned and synced repos redundantly store all available information |
| 120 | about that project, so if any one repo is lost, all of the cloned |
| 121 | historical content of the project as of the last sync is preserved |
| 122 | in each surviving repo. |
| 123 |