Fossil SCM
Add section "Naming of Files, Checkins, and Branches"
Commit
590a8fcac60f6cd8887c4d20ef9862eef1e8d126927e06a5dfb688cc2a9b00ba
Parent
986bde2b54df73d…
1 file changed
+24
+24
| --- www/quickstart.wiki | ||
| +++ www/quickstart.wiki | ||
| @@ -267,10 +267,34 @@ | ||
| 267 | 267 | <p>To commit your changes to a repository that was cloned from remote you |
| 268 | 268 | perform the same actions but the results are different. Fossil |
| 269 | 269 | defaults to 'autosync' mode, a single-stage commit that sends all changes |
| 270 | 270 | committed to the local repository immediately on to the remote parent repository. This |
| 271 | 271 | only works if you have write permission to the remote respository.</p> |
| 272 | + | |
| 273 | +<h2 id="naming">Naming of Files, Checkins, and Branches</h2> | |
| 274 | + | |
| 275 | + <p>Fossil deals with information artifacts. This Quickstart document only deals | |
| 276 | + with files and collections of files, but be aware there are also tickets, wiki pages and more. | |
| 277 | + Every artifact in Fossil has a universally-unique hash id, and may also have a | |
| 278 | + human-readable name.</p> | |
| 279 | + | |
| 280 | + <p>The following are all equivalent ways of identifying a Fossil file, | |
| 281 | + checkin or branch artifact:</p> | |
| 282 | + | |
| 283 | + <ul> | |
| 284 | + <li> the full unique SHA-256 hash, such as be836de35a821523beac2e53168e135d5ebd725d7af421e5f736a28e8034673a | |
| 285 | + <li> an abbreviated hash prefix, such as the first ten characters: be836de35a . This won't be universally unique, but it is usually unique within any one repository. As an example, the [https://fossil-scm.org/home/hash-collisions|Fossil project hash collisions] showed at the time of writing that there are no artifacts with identical first 8 characters | |
| 286 | + <li> a branch name, such as "special-features" or "juliet-testing". Each branch also has a unique SHA-256 hash | |
| 287 | + </ul> | |
| 288 | + | |
| 289 | + <p>A special convenience branch is "trunk", which is Fossil's default branch name for | |
| 290 | + the first checkin, and the default for any time a branch name is needed but not | |
| 291 | + specified.</p> | |
| 292 | + | |
| 293 | + This will get you started on identifying checkins. The | |
| 294 | + <a href="./checkin_names.wiki">Checkin Names document</a> is a complete reference, including | |
| 295 | + how timestamps can also be used. | |
| 272 | 296 | |
| 273 | 297 | <h2 id="config">Configuring Your Local Repository</h2> |
| 274 | 298 | |
| 275 | 299 | <p>When you create a new repository, either by cloning an existing |
| 276 | 300 | project or create a new project of your own, you usually want to do some |
| 277 | 301 |
| --- www/quickstart.wiki | |
| +++ www/quickstart.wiki | |
| @@ -267,10 +267,34 @@ | |
| 267 | <p>To commit your changes to a repository that was cloned from remote you |
| 268 | perform the same actions but the results are different. Fossil |
| 269 | defaults to 'autosync' mode, a single-stage commit that sends all changes |
| 270 | committed to the local repository immediately on to the remote parent repository. This |
| 271 | only works if you have write permission to the remote respository.</p> |
| 272 | |
| 273 | <h2 id="config">Configuring Your Local Repository</h2> |
| 274 | |
| 275 | <p>When you create a new repository, either by cloning an existing |
| 276 | project or create a new project of your own, you usually want to do some |
| 277 |
| --- www/quickstart.wiki | |
| +++ www/quickstart.wiki | |
| @@ -267,10 +267,34 @@ | |
| 267 | <p>To commit your changes to a repository that was cloned from remote you |
| 268 | perform the same actions but the results are different. Fossil |
| 269 | defaults to 'autosync' mode, a single-stage commit that sends all changes |
| 270 | committed to the local repository immediately on to the remote parent repository. This |
| 271 | only works if you have write permission to the remote respository.</p> |
| 272 | |
| 273 | <h2 id="naming">Naming of Files, Checkins, and Branches</h2> |
| 274 | |
| 275 | <p>Fossil deals with information artifacts. This Quickstart document only deals |
| 276 | with files and collections of files, but be aware there are also tickets, wiki pages and more. |
| 277 | Every artifact in Fossil has a universally-unique hash id, and may also have a |
| 278 | human-readable name.</p> |
| 279 | |
| 280 | <p>The following are all equivalent ways of identifying a Fossil file, |
| 281 | checkin or branch artifact:</p> |
| 282 | |
| 283 | <ul> |
| 284 | <li> the full unique SHA-256 hash, such as be836de35a821523beac2e53168e135d5ebd725d7af421e5f736a28e8034673a |
| 285 | <li> an abbreviated hash prefix, such as the first ten characters: be836de35a . This won't be universally unique, but it is usually unique within any one repository. As an example, the [https://fossil-scm.org/home/hash-collisions|Fossil project hash collisions] showed at the time of writing that there are no artifacts with identical first 8 characters |
| 286 | <li> a branch name, such as "special-features" or "juliet-testing". Each branch also has a unique SHA-256 hash |
| 287 | </ul> |
| 288 | |
| 289 | <p>A special convenience branch is "trunk", which is Fossil's default branch name for |
| 290 | the first checkin, and the default for any time a branch name is needed but not |
| 291 | specified.</p> |
| 292 | |
| 293 | This will get you started on identifying checkins. The |
| 294 | <a href="./checkin_names.wiki">Checkin Names document</a> is a complete reference, including |
| 295 | how timestamps can also be used. |
| 296 | |
| 297 | <h2 id="config">Configuring Your Local Repository</h2> |
| 298 | |
| 299 | <p>When you create a new repository, either by cloning an existing |
| 300 | project or create a new project of your own, you usually want to do some |
| 301 |