Fossil SCM
replace 'checkin' by 'check-in' in WWW-docs, except in links, arguments and combined words already containing a hyphen
Commit
3312e40f0f1a2394a8a6f2ca05527ec8c82a177c
Parent
b2f6c4b7ea216d7…
12 files changed
+1
-1
+2
-2
+8
-8
+1
-1
+1
-1
+1
-1
+1
-1
+3
-3
+1
-1
+1
-1
+5
-5
+3
-3
+1
-1
| --- www/branching.wiki | ||
| +++ www/branching.wiki | ||
| @@ -187,11 +187,11 @@ | ||
| 187 | 187 | as it encounters another check-in with the same tag. A cancellation tag |
| 188 | 188 | is attached to a single check-in in order to either override a one-time |
| 189 | 189 | tag that was previously placed on that same check-in, or to block |
| 190 | 190 | tag propagation from an ancestor. |
| 191 | 191 | |
| 192 | -The initial checkin of every repository has two propagating tags. In | |
| 192 | +The initial check-in of every repository has two propagating tags. In | |
| 193 | 193 | figure 5, that initial check-in is check-in 1. The <b>branch</b> tag |
| 194 | 194 | tells (by its value) what branch the check-in is a member of. |
| 195 | 195 | The default branch is called "trunk." All tags that begin with "<b>sym-</b>" |
| 196 | 196 | are symbolic name tags. When a symbolic name tag is attached to a |
| 197 | 197 | check-in, that allows you to refer to that check-in by its symbolic |
| 198 | 198 |
| --- www/branching.wiki | |
| +++ www/branching.wiki | |
| @@ -187,11 +187,11 @@ | |
| 187 | as it encounters another check-in with the same tag. A cancellation tag |
| 188 | is attached to a single check-in in order to either override a one-time |
| 189 | tag that was previously placed on that same check-in, or to block |
| 190 | tag propagation from an ancestor. |
| 191 | |
| 192 | The initial checkin of every repository has two propagating tags. In |
| 193 | figure 5, that initial check-in is check-in 1. The <b>branch</b> tag |
| 194 | tells (by its value) what branch the check-in is a member of. |
| 195 | The default branch is called "trunk." All tags that begin with "<b>sym-</b>" |
| 196 | are symbolic name tags. When a symbolic name tag is attached to a |
| 197 | check-in, that allows you to refer to that check-in by its symbolic |
| 198 |
| --- www/branching.wiki | |
| +++ www/branching.wiki | |
| @@ -187,11 +187,11 @@ | |
| 187 | as it encounters another check-in with the same tag. A cancellation tag |
| 188 | is attached to a single check-in in order to either override a one-time |
| 189 | tag that was previously placed on that same check-in, or to block |
| 190 | tag propagation from an ancestor. |
| 191 | |
| 192 | The initial check-in of every repository has two propagating tags. In |
| 193 | figure 5, that initial check-in is check-in 1. The <b>branch</b> tag |
| 194 | tells (by its value) what branch the check-in is a member of. |
| 195 | The default branch is called "trunk." All tags that begin with "<b>sym-</b>" |
| 196 | are symbolic name tags. When a symbolic name tag is attached to a |
| 197 | check-in, that allows you to refer to that check-in by its symbolic |
| 198 |
+2
-2
| --- www/changes.wiki | ||
| +++ www/changes.wiki | ||
| @@ -406,11 +406,11 @@ | ||
| 406 | 406 | host. |
| 407 | 407 | * On Windows, make the "gdiff" command default to use WinDiff.exe. |
| 408 | 408 | * Update the "fossil stash" command so that it always prompts for a |
| 409 | 409 | comment if the -m option is omitted. |
| 410 | 410 | * Enhance the timeline webpages so that a=, b=, c=, d=, p=, and dp= |
| 411 | - query parameters (and others) can all accept any valid checkin name | |
| 411 | + query parameters (and others) can all accept any valid check-in name | |
| 412 | 412 | (such as branch names or labels) instead of just SHA1 hashes. |
| 413 | 413 | * Added the "fossil stash show" command. |
| 414 | 414 | * Added the "fileage" webpage with links to this page from the check-in |
| 415 | 415 | information page and from the file browser. |
| 416 | 416 | * Added --age and -t options to the "fossil ls" command. |
| @@ -563,11 +563,11 @@ | ||
| 563 | 563 | * Fixed constant prompting regarding previously-saved SSL |
| 564 | 564 | certificates. [636804745b] |
| 565 | 565 | * Other SSL improvements. |
| 566 | 566 | * Added -R REPOFILE support to several more CLI commands. [e080560378] |
| 567 | 567 | * Generated tarballs now have constant timestamps, so they are |
| 568 | - always identical for any given checkin. [e080560378] | |
| 568 | + always identical for any given check-in. [e080560378] | |
| 569 | 569 | * A number of minor HTML-related tweaks and fixes. |
| 570 | 570 | * Added --args FILENAME global CLI argument to import arbitrary |
| 571 | 571 | CLI arguments from a file (e.g. long file lists). [e080560378] |
| 572 | 572 | * Fixed significant memory leak in annotation of files with long |
| 573 | 573 | histories.[9929bab702] |
| 574 | 574 |
| --- www/changes.wiki | |
| +++ www/changes.wiki | |
| @@ -406,11 +406,11 @@ | |
| 406 | host. |
| 407 | * On Windows, make the "gdiff" command default to use WinDiff.exe. |
| 408 | * Update the "fossil stash" command so that it always prompts for a |
| 409 | comment if the -m option is omitted. |
| 410 | * Enhance the timeline webpages so that a=, b=, c=, d=, p=, and dp= |
| 411 | query parameters (and others) can all accept any valid checkin name |
| 412 | (such as branch names or labels) instead of just SHA1 hashes. |
| 413 | * Added the "fossil stash show" command. |
| 414 | * Added the "fileage" webpage with links to this page from the check-in |
| 415 | information page and from the file browser. |
| 416 | * Added --age and -t options to the "fossil ls" command. |
| @@ -563,11 +563,11 @@ | |
| 563 | * Fixed constant prompting regarding previously-saved SSL |
| 564 | certificates. [636804745b] |
| 565 | * Other SSL improvements. |
| 566 | * Added -R REPOFILE support to several more CLI commands. [e080560378] |
| 567 | * Generated tarballs now have constant timestamps, so they are |
| 568 | always identical for any given checkin. [e080560378] |
| 569 | * A number of minor HTML-related tweaks and fixes. |
| 570 | * Added --args FILENAME global CLI argument to import arbitrary |
| 571 | CLI arguments from a file (e.g. long file lists). [e080560378] |
| 572 | * Fixed significant memory leak in annotation of files with long |
| 573 | histories.[9929bab702] |
| 574 |
| --- www/changes.wiki | |
| +++ www/changes.wiki | |
| @@ -406,11 +406,11 @@ | |
| 406 | host. |
| 407 | * On Windows, make the "gdiff" command default to use WinDiff.exe. |
| 408 | * Update the "fossil stash" command so that it always prompts for a |
| 409 | comment if the -m option is omitted. |
| 410 | * Enhance the timeline webpages so that a=, b=, c=, d=, p=, and dp= |
| 411 | query parameters (and others) can all accept any valid check-in name |
| 412 | (such as branch names or labels) instead of just SHA1 hashes. |
| 413 | * Added the "fossil stash show" command. |
| 414 | * Added the "fileage" webpage with links to this page from the check-in |
| 415 | information page and from the file browser. |
| 416 | * Added --age and -t options to the "fossil ls" command. |
| @@ -563,11 +563,11 @@ | |
| 563 | * Fixed constant prompting regarding previously-saved SSL |
| 564 | certificates. [636804745b] |
| 565 | * Other SSL improvements. |
| 566 | * Added -R REPOFILE support to several more CLI commands. [e080560378] |
| 567 | * Generated tarballs now have constant timestamps, so they are |
| 568 | always identical for any given check-in. [e080560378] |
| 569 | * A number of minor HTML-related tweaks and fixes. |
| 570 | * Added --args FILENAME global CLI argument to import arbitrary |
| 571 | CLI arguments from a file (e.g. long file lists). [e080560378] |
| 572 | * Fixed significant memory leak in annotation of files with long |
| 573 | histories.[9929bab702] |
| 574 |
+8
-8
| --- www/checkin_names.wiki | ||
| +++ www/checkin_names.wiki | ||
| @@ -43,11 +43,11 @@ | ||
| 43 | 43 | Fossil provides a variety of ways to specify a check-in. This |
| 44 | 44 | document describes the various methods. |
| 45 | 45 | |
| 46 | 46 | <h2>Canonical Check-in Name</h2> |
| 47 | 47 | |
| 48 | -The canonical name of a checkin is the SHA1 hash of its | |
| 48 | +The canonical name of a check-in is the SHA1 hash of its | |
| 49 | 49 | [./fileformat.wiki#manifest | manifest] expressed as a 40-character |
| 50 | 50 | lowercase hexadecimal number. For example: |
| 51 | 51 | |
| 52 | 52 | <blockquote><pre> |
| 53 | 53 | fossil info e5a734a19a9826973e1d073b49dc2a16aa2308f9 |
| @@ -117,24 +117,24 @@ | ||
| 117 | 117 | tagged with "deed2" not to the |
| 118 | 118 | check-in whose canonical name begins with "deed2". |
| 119 | 119 | |
| 120 | 120 | <h2>Whole Branches</h2> |
| 121 | 121 | |
| 122 | -Usually when a branch name is specified, it means the latest checkin on | |
| 122 | +Usually when a branch name is specified, it means the latest check-in on | |
| 123 | 123 | that branch. But for some commands (ex: [/help/purge|purge]) a branch name |
| 124 | -on the argument means the earliest connected checkin on the branch. This | |
| 124 | +on the argument means the earliest connected check-in on the branch. This | |
| 125 | 125 | seems confusing when being explained here, but it works out to be intuitive |
| 126 | 126 | in practice. |
| 127 | 127 | |
| 128 | -For example, the command "fossil purge XYZ" means to purge the checkin XYZ | |
| 128 | +For example, the command "fossil purge XYZ" means to purge the check-in XYZ | |
| 129 | 129 | and all of its descendants. But when XYZ is in the form of a branch name, one |
| 130 | -generally wants to purge the entire branch, not just the last checkin on the | |
| 130 | +generally wants to purge the entire branch, not just the last check-in on the | |
| 131 | 131 | branch. And so for this reason, commands like purge will interpret a branch |
| 132 | -name to be the first checkin of the branch rather than the last. If there | |
| 132 | +name to be the first check-in of the branch rather than the last. If there | |
| 133 | 133 | are two or more branches with the same name, then these commands will select |
| 134 | -the first check-in of the branch that has the most recent checkin. What | |
| 135 | -happens is that Fossil searches for the most recent checkin with the given | |
| 134 | +the first check-in of the branch that has the most recent check-in. What | |
| 135 | +happens is that Fossil searches for the most recent check-in with the given | |
| 136 | 136 | tag, just as it always does. But if that tag is a branch name, it then walks |
| 137 | 137 | back down the branch looking for the first check-in of that branch. |
| 138 | 138 | |
| 139 | 139 | Again, this behavior only occurs on a few commands where it make sense. |
| 140 | 140 | |
| 141 | 141 |
| --- www/checkin_names.wiki | |
| +++ www/checkin_names.wiki | |
| @@ -43,11 +43,11 @@ | |
| 43 | Fossil provides a variety of ways to specify a check-in. This |
| 44 | document describes the various methods. |
| 45 | |
| 46 | <h2>Canonical Check-in Name</h2> |
| 47 | |
| 48 | The canonical name of a checkin is the SHA1 hash of its |
| 49 | [./fileformat.wiki#manifest | manifest] expressed as a 40-character |
| 50 | lowercase hexadecimal number. For example: |
| 51 | |
| 52 | <blockquote><pre> |
| 53 | fossil info e5a734a19a9826973e1d073b49dc2a16aa2308f9 |
| @@ -117,24 +117,24 @@ | |
| 117 | tagged with "deed2" not to the |
| 118 | check-in whose canonical name begins with "deed2". |
| 119 | |
| 120 | <h2>Whole Branches</h2> |
| 121 | |
| 122 | Usually when a branch name is specified, it means the latest checkin on |
| 123 | that branch. But for some commands (ex: [/help/purge|purge]) a branch name |
| 124 | on the argument means the earliest connected checkin on the branch. This |
| 125 | seems confusing when being explained here, but it works out to be intuitive |
| 126 | in practice. |
| 127 | |
| 128 | For example, the command "fossil purge XYZ" means to purge the checkin XYZ |
| 129 | and all of its descendants. But when XYZ is in the form of a branch name, one |
| 130 | generally wants to purge the entire branch, not just the last checkin on the |
| 131 | branch. And so for this reason, commands like purge will interpret a branch |
| 132 | name to be the first checkin of the branch rather than the last. If there |
| 133 | are two or more branches with the same name, then these commands will select |
| 134 | the first check-in of the branch that has the most recent checkin. What |
| 135 | happens is that Fossil searches for the most recent checkin with the given |
| 136 | tag, just as it always does. But if that tag is a branch name, it then walks |
| 137 | back down the branch looking for the first check-in of that branch. |
| 138 | |
| 139 | Again, this behavior only occurs on a few commands where it make sense. |
| 140 | |
| 141 |
| --- www/checkin_names.wiki | |
| +++ www/checkin_names.wiki | |
| @@ -43,11 +43,11 @@ | |
| 43 | Fossil provides a variety of ways to specify a check-in. This |
| 44 | document describes the various methods. |
| 45 | |
| 46 | <h2>Canonical Check-in Name</h2> |
| 47 | |
| 48 | The canonical name of a check-in is the SHA1 hash of its |
| 49 | [./fileformat.wiki#manifest | manifest] expressed as a 40-character |
| 50 | lowercase hexadecimal number. For example: |
| 51 | |
| 52 | <blockquote><pre> |
| 53 | fossil info e5a734a19a9826973e1d073b49dc2a16aa2308f9 |
| @@ -117,24 +117,24 @@ | |
| 117 | tagged with "deed2" not to the |
| 118 | check-in whose canonical name begins with "deed2". |
| 119 | |
| 120 | <h2>Whole Branches</h2> |
| 121 | |
| 122 | Usually when a branch name is specified, it means the latest check-in on |
| 123 | that branch. But for some commands (ex: [/help/purge|purge]) a branch name |
| 124 | on the argument means the earliest connected check-in on the branch. This |
| 125 | seems confusing when being explained here, but it works out to be intuitive |
| 126 | in practice. |
| 127 | |
| 128 | For example, the command "fossil purge XYZ" means to purge the check-in XYZ |
| 129 | and all of its descendants. But when XYZ is in the form of a branch name, one |
| 130 | generally wants to purge the entire branch, not just the last check-in on the |
| 131 | branch. And so for this reason, commands like purge will interpret a branch |
| 132 | name to be the first check-in of the branch rather than the last. If there |
| 133 | are two or more branches with the same name, then these commands will select |
| 134 | the first check-in of the branch that has the most recent check-in. What |
| 135 | happens is that Fossil searches for the most recent check-in with the given |
| 136 | tag, just as it always does. But if that tag is a branch name, it then walks |
| 137 | back down the branch looking for the first check-in of that branch. |
| 138 | |
| 139 | Again, this behavior only occurs on a few commands where it make sense. |
| 140 | |
| 141 |
+1
-1
| --- www/contribute.wiki | ||
| +++ www/contribute.wiki | ||
| @@ -51,11 +51,11 @@ | ||
| 51 | 51 | |
| 52 | 52 | Contributors are asked to make all non-trivial changes on a branch. The |
| 53 | 53 | Fossil Architect (Richard Hipp) will merge changes onto the trunk.</p> |
| 54 | 54 | |
| 55 | 55 | Contributors are required to following the |
| 56 | -[./checkin.wiki | pre-checkin checklist] prior to every checkin to | |
| 56 | +[./checkin.wiki | pre-checkin checklist] prior to every check-in to | |
| 57 | 57 | the Fossil self-hosting repository. This checklist is short and succinct |
| 58 | 58 | and should only require a few seconds to follow. Contributors |
| 59 | 59 | should print out a copy of the pre-checkin checklist and keep |
| 60 | 60 | it on a notecard beside their workstations, for quick reference. |
| 61 | 61 | |
| 62 | 62 |
| --- www/contribute.wiki | |
| +++ www/contribute.wiki | |
| @@ -51,11 +51,11 @@ | |
| 51 | |
| 52 | Contributors are asked to make all non-trivial changes on a branch. The |
| 53 | Fossil Architect (Richard Hipp) will merge changes onto the trunk.</p> |
| 54 | |
| 55 | Contributors are required to following the |
| 56 | [./checkin.wiki | pre-checkin checklist] prior to every checkin to |
| 57 | the Fossil self-hosting repository. This checklist is short and succinct |
| 58 | and should only require a few seconds to follow. Contributors |
| 59 | should print out a copy of the pre-checkin checklist and keep |
| 60 | it on a notecard beside their workstations, for quick reference. |
| 61 | |
| 62 |
| --- www/contribute.wiki | |
| +++ www/contribute.wiki | |
| @@ -51,11 +51,11 @@ | |
| 51 | |
| 52 | Contributors are asked to make all non-trivial changes on a branch. The |
| 53 | Fossil Architect (Richard Hipp) will merge changes onto the trunk.</p> |
| 54 | |
| 55 | Contributors are required to following the |
| 56 | [./checkin.wiki | pre-checkin checklist] prior to every check-in to |
| 57 | the Fossil self-hosting repository. This checklist is short and succinct |
| 58 | and should only require a few seconds to follow. Contributors |
| 59 | should print out a copy of the pre-checkin checklist and keep |
| 60 | it on a notecard beside their workstations, for quick reference. |
| 61 | |
| 62 |
+1
-1
| --- www/fileformat.wiki | ||
| +++ www/fileformat.wiki | ||
| @@ -113,11 +113,11 @@ | ||
| 113 | 113 | A manifest may optionally have a single B-card. The B-card specifies |
| 114 | 114 | another manifest that serves as the "baseline" for this manifest. A |
| 115 | 115 | manifest that has a B-card is called a delta-manifest and a manifest |
| 116 | 116 | that omits the B-card is a baseline-manifest. The other manifest |
| 117 | 117 | identified by the argument of the B-card must be a baseline-manifest. |
| 118 | -A baseline-manifest records the complete contents of a checkin. | |
| 118 | +A baseline-manifest records the complete contents of a check-in. | |
| 119 | 119 | A delta-manifest records only changes from its baseline. |
| 120 | 120 | |
| 121 | 121 | A manifest must have exactly one C-card. The sole argument to |
| 122 | 122 | the C-card is a check-in comment that describes the check-in that |
| 123 | 123 | the manifest defines. The check-in comment is text. The following |
| 124 | 124 |
| --- www/fileformat.wiki | |
| +++ www/fileformat.wiki | |
| @@ -113,11 +113,11 @@ | |
| 113 | A manifest may optionally have a single B-card. The B-card specifies |
| 114 | another manifest that serves as the "baseline" for this manifest. A |
| 115 | manifest that has a B-card is called a delta-manifest and a manifest |
| 116 | that omits the B-card is a baseline-manifest. The other manifest |
| 117 | identified by the argument of the B-card must be a baseline-manifest. |
| 118 | A baseline-manifest records the complete contents of a checkin. |
| 119 | A delta-manifest records only changes from its baseline. |
| 120 | |
| 121 | A manifest must have exactly one C-card. The sole argument to |
| 122 | the C-card is a check-in comment that describes the check-in that |
| 123 | the manifest defines. The check-in comment is text. The following |
| 124 |
| --- www/fileformat.wiki | |
| +++ www/fileformat.wiki | |
| @@ -113,11 +113,11 @@ | |
| 113 | A manifest may optionally have a single B-card. The B-card specifies |
| 114 | another manifest that serves as the "baseline" for this manifest. A |
| 115 | manifest that has a B-card is called a delta-manifest and a manifest |
| 116 | that omits the B-card is a baseline-manifest. The other manifest |
| 117 | identified by the argument of the B-card must be a baseline-manifest. |
| 118 | A baseline-manifest records the complete contents of a check-in. |
| 119 | A delta-manifest records only changes from its baseline. |
| 120 | |
| 121 | A manifest must have exactly one C-card. The sole argument to |
| 122 | the C-card is a check-in comment that describes the check-in that |
| 123 | the manifest defines. The check-in comment is text. The following |
| 124 |
+1
-1
| --- www/hints.wiki | ||
| +++ www/hints.wiki | ||
| @@ -28,11 +28,11 @@ | ||
| 28 | 28 | URL to get any number of records you desire. To see a complete |
| 29 | 29 | timeline graph, set n to some ridiculously large value like 10000000. |
| 30 | 30 | |
| 31 | 31 | 6. You can manually add a "c=CHECKIN" query parameter to the timeline |
| 32 | 32 | URL to get a snapshot of what was going on about the time of some |
| 33 | - checkin. The "CHECKIN" can be | |
| 33 | + check-in. The "CHECKIN" can be | |
| 34 | 34 | [./checkin_names.wiki | any valid check-in or version name], including |
| 35 | 35 | tags, branch names, and dates. For example, to see what was going |
| 36 | 36 | on in the Fossil repository on 2008-01-01, visit |
| 37 | 37 | [http://www.fossil-scm.org/fossil/timeline?c=2008-01-01]. |
| 38 | 38 | |
| 39 | 39 |
| --- www/hints.wiki | |
| +++ www/hints.wiki | |
| @@ -28,11 +28,11 @@ | |
| 28 | URL to get any number of records you desire. To see a complete |
| 29 | timeline graph, set n to some ridiculously large value like 10000000. |
| 30 | |
| 31 | 6. You can manually add a "c=CHECKIN" query parameter to the timeline |
| 32 | URL to get a snapshot of what was going on about the time of some |
| 33 | checkin. The "CHECKIN" can be |
| 34 | [./checkin_names.wiki | any valid check-in or version name], including |
| 35 | tags, branch names, and dates. For example, to see what was going |
| 36 | on in the Fossil repository on 2008-01-01, visit |
| 37 | [http://www.fossil-scm.org/fossil/timeline?c=2008-01-01]. |
| 38 | |
| 39 |
| --- www/hints.wiki | |
| +++ www/hints.wiki | |
| @@ -28,11 +28,11 @@ | |
| 28 | URL to get any number of records you desire. To see a complete |
| 29 | timeline graph, set n to some ridiculously large value like 10000000. |
| 30 | |
| 31 | 6. You can manually add a "c=CHECKIN" query parameter to the timeline |
| 32 | URL to get a snapshot of what was going on about the time of some |
| 33 | check-in. The "CHECKIN" can be |
| 34 | [./checkin_names.wiki | any valid check-in or version name], including |
| 35 | tags, branch names, and dates. For example, to see what was going |
| 36 | on in the Fossil repository on 2008-01-01, visit |
| 37 | [http://www.fossil-scm.org/fossil/timeline?c=2008-01-01]. |
| 38 | |
| 39 |
+1
-1
| --- www/mkindex.tcl | ||
| +++ www/mkindex.tcl | ||
| @@ -11,11 +11,11 @@ | ||
| 11 | 11 | adding_code.wiki {Hacking Fossil} |
| 12 | 12 | antibot.wiki {Defense against Spiders and Bots} |
| 13 | 13 | bugtheory.wiki {Bug Tracking In Fossil} |
| 14 | 14 | branching.wiki {Branching, Forking, Merging, and Tagging} |
| 15 | 15 | build.wiki {Compiling and Installing Fossil} |
| 16 | - checkin_names.wiki {Checkin And Version Names} | |
| 16 | + checkin_names.wiki {Check-in And Version Names} | |
| 17 | 17 | checkin.wiki {Check-in Checklist} |
| 18 | 18 | changes.wiki {Fossil Changelog} |
| 19 | 19 | copyright-release.html {Contributor License Agreement} |
| 20 | 20 | concepts.wiki {Fossil Core Concepts} |
| 21 | 21 | contribute.wiki {Contributing Code or Documentation To The Fossil Project} |
| 22 | 22 |
| --- www/mkindex.tcl | |
| +++ www/mkindex.tcl | |
| @@ -11,11 +11,11 @@ | |
| 11 | adding_code.wiki {Hacking Fossil} |
| 12 | antibot.wiki {Defense against Spiders and Bots} |
| 13 | bugtheory.wiki {Bug Tracking In Fossil} |
| 14 | branching.wiki {Branching, Forking, Merging, and Tagging} |
| 15 | build.wiki {Compiling and Installing Fossil} |
| 16 | checkin_names.wiki {Checkin And Version Names} |
| 17 | checkin.wiki {Check-in Checklist} |
| 18 | changes.wiki {Fossil Changelog} |
| 19 | copyright-release.html {Contributor License Agreement} |
| 20 | concepts.wiki {Fossil Core Concepts} |
| 21 | contribute.wiki {Contributing Code or Documentation To The Fossil Project} |
| 22 |
| --- www/mkindex.tcl | |
| +++ www/mkindex.tcl | |
| @@ -11,11 +11,11 @@ | |
| 11 | adding_code.wiki {Hacking Fossil} |
| 12 | antibot.wiki {Defense against Spiders and Bots} |
| 13 | bugtheory.wiki {Bug Tracking In Fossil} |
| 14 | branching.wiki {Branching, Forking, Merging, and Tagging} |
| 15 | build.wiki {Compiling and Installing Fossil} |
| 16 | checkin_names.wiki {Check-in And Version Names} |
| 17 | checkin.wiki {Check-in Checklist} |
| 18 | changes.wiki {Fossil Changelog} |
| 19 | copyright-release.html {Contributor License Agreement} |
| 20 | concepts.wiki {Fossil Core Concepts} |
| 21 | contribute.wiki {Contributing Code or Documentation To The Fossil Project} |
| 22 |
+3
-3
| --- www/permutedindex.html | ||
| +++ www/permutedindex.html | ||
| @@ -35,11 +35,11 @@ | ||
| 35 | 35 | <li><a href="branching.wiki">Branching, Forking, Merging, and Tagging</a></li> |
| 36 | 36 | <li><a href="bugtheory.wiki">Bug Tracking In Fossil</a></li> |
| 37 | 37 | <li><a href="makefile.wiki">Build Process — The Fossil</a></li> |
| 38 | 38 | <li><a href="changes.wiki">Changelog — Fossil</a></li> |
| 39 | 39 | <li><a href="checkin.wiki">Check-in Checklist</a></li> |
| 40 | -<li><a href="checkin_names.wiki">Checkin And Version Names</a></li> | |
| 40 | +<li><a href="checkin_names.wiki">Check-in And Version Names</a></li> | |
| 41 | 41 | <li><a href="checkin.wiki">Checklist — Check-in</a></li> |
| 42 | 42 | <li><a href="../test/release-checklist.wiki">Checklist — Pre-Release Testing</a></li> |
| 43 | 43 | <li><a href="foss-cklist.wiki">Checklist For Successful Open-Source Projects</a></li> |
| 44 | 44 | <li><a href="selfcheck.wiki">Checks — Fossil Repository Integrity Self</a></li> |
| 45 | 45 | <li><a href="contribute.wiki">Code or Documentation To The Fossil Project — Contributing</a></li> |
| @@ -118,11 +118,11 @@ | ||
| 118 | 118 | <li><a href="copyright-release.html">License Agreement — Contributor</a></li> |
| 119 | 119 | <li><a href="password.wiki">Management And Authentication — Password</a></li> |
| 120 | 120 | <li><a href="branching.wiki">Merging, and Tagging — Branching, Forking,</a></li> |
| 121 | 121 | <li><a href="fossil-from-msvc.wiki">Microsoft Express 2010 IDE — Integrating Fossil in the</a></li> |
| 122 | 122 | <li><a href="fiveminutes.wiki">Minutes as a Single User — Update and Running in 5</a></li> |
| 123 | -<li><a href="checkin_names.wiki">Names — Checkin And Version</a></li> | |
| 123 | +<li><a href="checkin_names.wiki">Names — Check-in And Version</a></li> | |
| 124 | 124 | <li><a href="adding_code.wiki">New Features To Fossil — Adding</a></li> |
| 125 | 125 | <li><a href="newrepo.wiki">New Fossil Repository — How To Create A</a></li> |
| 126 | 126 | <li><a href="foss-cklist.wiki">Open-Source Projects — Checklist For Successful</a></li> |
| 127 | 127 | <li><a href="pop.wiki">Operations — Principles Of</a></li> |
| 128 | 128 | <li><a href="tech_overview.wiki">Overview Of The Design And Implementation Of Fossil — A Technical</a></li> |
| @@ -185,13 +185,13 @@ | ||
| 185 | 185 | <li><a href="bugtheory.wiki">Tracking In Fossil — Bug</a></li> |
| 186 | 186 | <li><a href="fiveminutes.wiki">Update and Running in 5 Minutes as a Single User</a></li> |
| 187 | 187 | <li><a href="hints.wiki">Usage Hints — Fossil Tips And</a></li> |
| 188 | 188 | <li><a href="fiveminutes.wiki">User — Update and Running in 5 Minutes as a Single</a></li> |
| 189 | 189 | <li><a href="ssl.wiki">Using SSL with Fossil</a></li> |
| 190 | -<li><a href="checkin_names.wiki">Version Names — Checkin And</a></li> | |
| 190 | +<li><a href="checkin_names.wiki">Version Names — Check-in And</a></li> | |
| 191 | 191 | <li><a href="fossil-v-git.wiki">Versus Git — Fossil</a></li> |
| 192 | 192 | <li><a href="webui.wiki">Web Interface — The Fossil</a></li> |
| 193 | 193 | <li><a href="customskin.md">Web Pages — Theming: Customizing The Appearance of</a></li> |
| 194 | 194 | <li><a href="quotes.wiki">What People Are Saying About Fossil, Git, and DVCSes in General — Quotes:</a></li> |
| 195 | 195 | <li><a href="wikitheory.wiki">Wiki In Fossil</a></li> |
| 196 | 196 | <li><a href="ssl.wiki">with Fossil — Using SSL</a></li> |
| 197 | 197 | </ul></div> |
| 198 | 198 |
| --- www/permutedindex.html | |
| +++ www/permutedindex.html | |
| @@ -35,11 +35,11 @@ | |
| 35 | <li><a href="branching.wiki">Branching, Forking, Merging, and Tagging</a></li> |
| 36 | <li><a href="bugtheory.wiki">Bug Tracking In Fossil</a></li> |
| 37 | <li><a href="makefile.wiki">Build Process — The Fossil</a></li> |
| 38 | <li><a href="changes.wiki">Changelog — Fossil</a></li> |
| 39 | <li><a href="checkin.wiki">Check-in Checklist</a></li> |
| 40 | <li><a href="checkin_names.wiki">Checkin And Version Names</a></li> |
| 41 | <li><a href="checkin.wiki">Checklist — Check-in</a></li> |
| 42 | <li><a href="../test/release-checklist.wiki">Checklist — Pre-Release Testing</a></li> |
| 43 | <li><a href="foss-cklist.wiki">Checklist For Successful Open-Source Projects</a></li> |
| 44 | <li><a href="selfcheck.wiki">Checks — Fossil Repository Integrity Self</a></li> |
| 45 | <li><a href="contribute.wiki">Code or Documentation To The Fossil Project — Contributing</a></li> |
| @@ -118,11 +118,11 @@ | |
| 118 | <li><a href="copyright-release.html">License Agreement — Contributor</a></li> |
| 119 | <li><a href="password.wiki">Management And Authentication — Password</a></li> |
| 120 | <li><a href="branching.wiki">Merging, and Tagging — Branching, Forking,</a></li> |
| 121 | <li><a href="fossil-from-msvc.wiki">Microsoft Express 2010 IDE — Integrating Fossil in the</a></li> |
| 122 | <li><a href="fiveminutes.wiki">Minutes as a Single User — Update and Running in 5</a></li> |
| 123 | <li><a href="checkin_names.wiki">Names — Checkin And Version</a></li> |
| 124 | <li><a href="adding_code.wiki">New Features To Fossil — Adding</a></li> |
| 125 | <li><a href="newrepo.wiki">New Fossil Repository — How To Create A</a></li> |
| 126 | <li><a href="foss-cklist.wiki">Open-Source Projects — Checklist For Successful</a></li> |
| 127 | <li><a href="pop.wiki">Operations — Principles Of</a></li> |
| 128 | <li><a href="tech_overview.wiki">Overview Of The Design And Implementation Of Fossil — A Technical</a></li> |
| @@ -185,13 +185,13 @@ | |
| 185 | <li><a href="bugtheory.wiki">Tracking In Fossil — Bug</a></li> |
| 186 | <li><a href="fiveminutes.wiki">Update and Running in 5 Minutes as a Single User</a></li> |
| 187 | <li><a href="hints.wiki">Usage Hints — Fossil Tips And</a></li> |
| 188 | <li><a href="fiveminutes.wiki">User — Update and Running in 5 Minutes as a Single</a></li> |
| 189 | <li><a href="ssl.wiki">Using SSL with Fossil</a></li> |
| 190 | <li><a href="checkin_names.wiki">Version Names — Checkin And</a></li> |
| 191 | <li><a href="fossil-v-git.wiki">Versus Git — Fossil</a></li> |
| 192 | <li><a href="webui.wiki">Web Interface — The Fossil</a></li> |
| 193 | <li><a href="customskin.md">Web Pages — Theming: Customizing The Appearance of</a></li> |
| 194 | <li><a href="quotes.wiki">What People Are Saying About Fossil, Git, and DVCSes in General — Quotes:</a></li> |
| 195 | <li><a href="wikitheory.wiki">Wiki In Fossil</a></li> |
| 196 | <li><a href="ssl.wiki">with Fossil — Using SSL</a></li> |
| 197 | </ul></div> |
| 198 |
| --- www/permutedindex.html | |
| +++ www/permutedindex.html | |
| @@ -35,11 +35,11 @@ | |
| 35 | <li><a href="branching.wiki">Branching, Forking, Merging, and Tagging</a></li> |
| 36 | <li><a href="bugtheory.wiki">Bug Tracking In Fossil</a></li> |
| 37 | <li><a href="makefile.wiki">Build Process — The Fossil</a></li> |
| 38 | <li><a href="changes.wiki">Changelog — Fossil</a></li> |
| 39 | <li><a href="checkin.wiki">Check-in Checklist</a></li> |
| 40 | <li><a href="checkin_names.wiki">Check-in And Version Names</a></li> |
| 41 | <li><a href="checkin.wiki">Checklist — Check-in</a></li> |
| 42 | <li><a href="../test/release-checklist.wiki">Checklist — Pre-Release Testing</a></li> |
| 43 | <li><a href="foss-cklist.wiki">Checklist For Successful Open-Source Projects</a></li> |
| 44 | <li><a href="selfcheck.wiki">Checks — Fossil Repository Integrity Self</a></li> |
| 45 | <li><a href="contribute.wiki">Code or Documentation To The Fossil Project — Contributing</a></li> |
| @@ -118,11 +118,11 @@ | |
| 118 | <li><a href="copyright-release.html">License Agreement — Contributor</a></li> |
| 119 | <li><a href="password.wiki">Management And Authentication — Password</a></li> |
| 120 | <li><a href="branching.wiki">Merging, and Tagging — Branching, Forking,</a></li> |
| 121 | <li><a href="fossil-from-msvc.wiki">Microsoft Express 2010 IDE — Integrating Fossil in the</a></li> |
| 122 | <li><a href="fiveminutes.wiki">Minutes as a Single User — Update and Running in 5</a></li> |
| 123 | <li><a href="checkin_names.wiki">Names — Check-in And Version</a></li> |
| 124 | <li><a href="adding_code.wiki">New Features To Fossil — Adding</a></li> |
| 125 | <li><a href="newrepo.wiki">New Fossil Repository — How To Create A</a></li> |
| 126 | <li><a href="foss-cklist.wiki">Open-Source Projects — Checklist For Successful</a></li> |
| 127 | <li><a href="pop.wiki">Operations — Principles Of</a></li> |
| 128 | <li><a href="tech_overview.wiki">Overview Of The Design And Implementation Of Fossil — A Technical</a></li> |
| @@ -185,13 +185,13 @@ | |
| 185 | <li><a href="bugtheory.wiki">Tracking In Fossil — Bug</a></li> |
| 186 | <li><a href="fiveminutes.wiki">Update and Running in 5 Minutes as a Single User</a></li> |
| 187 | <li><a href="hints.wiki">Usage Hints — Fossil Tips And</a></li> |
| 188 | <li><a href="fiveminutes.wiki">User — Update and Running in 5 Minutes as a Single</a></li> |
| 189 | <li><a href="ssl.wiki">Using SSL with Fossil</a></li> |
| 190 | <li><a href="checkin_names.wiki">Version Names — Check-in And</a></li> |
| 191 | <li><a href="fossil-v-git.wiki">Versus Git — Fossil</a></li> |
| 192 | <li><a href="webui.wiki">Web Interface — The Fossil</a></li> |
| 193 | <li><a href="customskin.md">Web Pages — Theming: Customizing The Appearance of</a></li> |
| 194 | <li><a href="quotes.wiki">What People Are Saying About Fossil, Git, and DVCSes in General — Quotes:</a></li> |
| 195 | <li><a href="wikitheory.wiki">Wiki In Fossil</a></li> |
| 196 | <li><a href="ssl.wiki">with Fossil — Using SSL</a></li> |
| 197 | </ul></div> |
| 198 |
+1
-1
| --- www/private.wiki | ||
| +++ www/private.wiki | ||
| @@ -16,11 +16,11 @@ | ||
| 16 | 16 | |
| 17 | 17 | The --private option causes Fossil to put the check-in in a new branch |
| 18 | 18 | named "private". That branch will not participate in subsequent clone, |
| 19 | 19 | sync, push, or pull operations. The branch will remain on the one local |
| 20 | 20 | repository where it was created. Note that you only use the --private |
| 21 | -option for the first checkin that creates the private branch. | |
| 21 | +option for the first check-in that creates the private branch. | |
| 22 | 22 | Additional checkins into the private branch remain private automatically. |
| 23 | 23 | |
| 24 | 24 | <h2>Publishing Private Changes</h2> |
| 25 | 25 | |
| 26 | 26 | After additional work, one might desire to publish the changes associated |
| 27 | 27 |
| --- www/private.wiki | |
| +++ www/private.wiki | |
| @@ -16,11 +16,11 @@ | |
| 16 | |
| 17 | The --private option causes Fossil to put the check-in in a new branch |
| 18 | named "private". That branch will not participate in subsequent clone, |
| 19 | sync, push, or pull operations. The branch will remain on the one local |
| 20 | repository where it was created. Note that you only use the --private |
| 21 | option for the first checkin that creates the private branch. |
| 22 | Additional checkins into the private branch remain private automatically. |
| 23 | |
| 24 | <h2>Publishing Private Changes</h2> |
| 25 | |
| 26 | After additional work, one might desire to publish the changes associated |
| 27 |
| --- www/private.wiki | |
| +++ www/private.wiki | |
| @@ -16,11 +16,11 @@ | |
| 16 | |
| 17 | The --private option causes Fossil to put the check-in in a new branch |
| 18 | named "private". That branch will not participate in subsequent clone, |
| 19 | sync, push, or pull operations. The branch will remain on the one local |
| 20 | repository where it was created. Note that you only use the --private |
| 21 | option for the first check-in that creates the private branch. |
| 22 | Additional checkins into the private branch remain private automatically. |
| 23 | |
| 24 | <h2>Publishing Private Changes</h2> |
| 25 | |
| 26 | After additional work, one might desire to publish the changes associated |
| 27 |
+1
-1
| --- www/selfcheck.wiki | ||
| +++ www/selfcheck.wiki | ||
| @@ -69,11 +69,11 @@ | ||
| 69 | 69 | <h2>Checksum Over All Files In A Check-in</h2> |
| 70 | 70 | |
| 71 | 71 | Manifest artifacts that define a check-in have two fields (the |
| 72 | 72 | R-card and Z-card) that record MD5 hashes of the manifest itself |
| 73 | 73 | and of all other files in the manifest. Prior to any check-in |
| 74 | -commit, these checksums are verified to ensure that the checkin | |
| 74 | +commit, these checksums are verified to ensure that the check-in | |
| 75 | 75 | agrees exactly with what is on disk. Similarly, |
| 76 | 76 | the repository checksum is verified after a checkout to make |
| 77 | 77 | sure that the entire repository was checked out correctly. |
| 78 | 78 | Note that these added checks use a different hash (MD5 instead |
| 79 | 79 | of SHA1) in order to avoid common-mode failures in the hash |
| 80 | 80 |
| --- www/selfcheck.wiki | |
| +++ www/selfcheck.wiki | |
| @@ -69,11 +69,11 @@ | |
| 69 | <h2>Checksum Over All Files In A Check-in</h2> |
| 70 | |
| 71 | Manifest artifacts that define a check-in have two fields (the |
| 72 | R-card and Z-card) that record MD5 hashes of the manifest itself |
| 73 | and of all other files in the manifest. Prior to any check-in |
| 74 | commit, these checksums are verified to ensure that the checkin |
| 75 | agrees exactly with what is on disk. Similarly, |
| 76 | the repository checksum is verified after a checkout to make |
| 77 | sure that the entire repository was checked out correctly. |
| 78 | Note that these added checks use a different hash (MD5 instead |
| 79 | of SHA1) in order to avoid common-mode failures in the hash |
| 80 |
| --- www/selfcheck.wiki | |
| +++ www/selfcheck.wiki | |
| @@ -69,11 +69,11 @@ | |
| 69 | <h2>Checksum Over All Files In A Check-in</h2> |
| 70 | |
| 71 | Manifest artifacts that define a check-in have two fields (the |
| 72 | R-card and Z-card) that record MD5 hashes of the manifest itself |
| 73 | and of all other files in the manifest. Prior to any check-in |
| 74 | commit, these checksums are verified to ensure that the check-in |
| 75 | agrees exactly with what is on disk. Similarly, |
| 76 | the repository checksum is verified after a checkout to make |
| 77 | sure that the entire repository was checked out correctly. |
| 78 | Note that these added checks use a different hash (MD5 instead |
| 79 | of SHA1) in order to avoid common-mode failures in the hash |
| 80 |
+5
-5
| --- www/tech_overview.wiki | ||
| +++ www/tech_overview.wiki | ||
| @@ -186,20 +186,20 @@ | ||
| 186 | 186 | |
| 187 | 187 | The global project state information in the repository database is |
| 188 | 188 | supplemented by computed metadata that makes querying the project state |
| 189 | 189 | more efficient. Metadata includes information such as the following: |
| 190 | 190 | |
| 191 | - * The names for all files found in any checkin. | |
| 191 | + * The names for all files found in any check-in. | |
| 192 | 192 | * All check-ins that modify a given file |
| 193 | - * Parents and children of each checkin. | |
| 193 | + * Parents and children of each check-in. | |
| 194 | 194 | * Potential timeline rows. |
| 195 | - * The names of all symbolic tags and the checkins they apply to. | |
| 195 | + * The names of all symbolic tags and the check-ins they apply to. | |
| 196 | 196 | * The names of all wiki pages and the artifacts that comprise each |
| 197 | 197 | wiki page. |
| 198 | 198 | * Attachments and the wiki pages or tickets they apply to. |
| 199 | 199 | * Current content of each ticket. |
| 200 | - * Cross-references between tickets, checkins, and wiki pages. | |
| 200 | + * Cross-references between tickets, check-ins, and wiki pages. | |
| 201 | 201 | |
| 202 | 202 | The metadata is held in various SQL tables in the repository database. |
| 203 | 203 | The metadata is designed to facilitate queries for the various timelines and |
| 204 | 204 | reports that Fossil generates. |
| 205 | 205 | As the functionality of Fossil evolves, |
| @@ -299,11 +299,11 @@ | ||
| 299 | 299 | * Files that have been [/help/add | added], |
| 300 | 300 | [/help/rm | removed], or [/help/mv | renamed] but not |
| 301 | 301 | yet committed. |
| 302 | 302 | * The mtime and size of files as they were originally checked out, |
| 303 | 303 | in order to expedite checking which files have been edited. |
| 304 | - * Other checkins that have been [/help/merge | merged] into the | |
| 304 | + * Other check-ins that have been [/help/merge | merged] into the | |
| 305 | 305 | working checkout but not yet committed. |
| 306 | 306 | * Copies of files prior to the most recent undoable operation - needed to |
| 307 | 307 | implement the [/help/undo | undo] and [/help/redo | redo] commands. |
| 308 | 308 | * The [/help/stash | stash]. |
| 309 | 309 | * State information for the [/help/bisect | bisect] command. |
| 310 | 310 |
| --- www/tech_overview.wiki | |
| +++ www/tech_overview.wiki | |
| @@ -186,20 +186,20 @@ | |
| 186 | |
| 187 | The global project state information in the repository database is |
| 188 | supplemented by computed metadata that makes querying the project state |
| 189 | more efficient. Metadata includes information such as the following: |
| 190 | |
| 191 | * The names for all files found in any checkin. |
| 192 | * All check-ins that modify a given file |
| 193 | * Parents and children of each checkin. |
| 194 | * Potential timeline rows. |
| 195 | * The names of all symbolic tags and the checkins they apply to. |
| 196 | * The names of all wiki pages and the artifacts that comprise each |
| 197 | wiki page. |
| 198 | * Attachments and the wiki pages or tickets they apply to. |
| 199 | * Current content of each ticket. |
| 200 | * Cross-references between tickets, checkins, and wiki pages. |
| 201 | |
| 202 | The metadata is held in various SQL tables in the repository database. |
| 203 | The metadata is designed to facilitate queries for the various timelines and |
| 204 | reports that Fossil generates. |
| 205 | As the functionality of Fossil evolves, |
| @@ -299,11 +299,11 @@ | |
| 299 | * Files that have been [/help/add | added], |
| 300 | [/help/rm | removed], or [/help/mv | renamed] but not |
| 301 | yet committed. |
| 302 | * The mtime and size of files as they were originally checked out, |
| 303 | in order to expedite checking which files have been edited. |
| 304 | * Other checkins that have been [/help/merge | merged] into the |
| 305 | working checkout but not yet committed. |
| 306 | * Copies of files prior to the most recent undoable operation - needed to |
| 307 | implement the [/help/undo | undo] and [/help/redo | redo] commands. |
| 308 | * The [/help/stash | stash]. |
| 309 | * State information for the [/help/bisect | bisect] command. |
| 310 |
| --- www/tech_overview.wiki | |
| +++ www/tech_overview.wiki | |
| @@ -186,20 +186,20 @@ | |
| 186 | |
| 187 | The global project state information in the repository database is |
| 188 | supplemented by computed metadata that makes querying the project state |
| 189 | more efficient. Metadata includes information such as the following: |
| 190 | |
| 191 | * The names for all files found in any check-in. |
| 192 | * All check-ins that modify a given file |
| 193 | * Parents and children of each check-in. |
| 194 | * Potential timeline rows. |
| 195 | * The names of all symbolic tags and the check-ins they apply to. |
| 196 | * The names of all wiki pages and the artifacts that comprise each |
| 197 | wiki page. |
| 198 | * Attachments and the wiki pages or tickets they apply to. |
| 199 | * Current content of each ticket. |
| 200 | * Cross-references between tickets, check-ins, and wiki pages. |
| 201 | |
| 202 | The metadata is held in various SQL tables in the repository database. |
| 203 | The metadata is designed to facilitate queries for the various timelines and |
| 204 | reports that Fossil generates. |
| 205 | As the functionality of Fossil evolves, |
| @@ -299,11 +299,11 @@ | |
| 299 | * Files that have been [/help/add | added], |
| 300 | [/help/rm | removed], or [/help/mv | renamed] but not |
| 301 | yet committed. |
| 302 | * The mtime and size of files as they were originally checked out, |
| 303 | in order to expedite checking which files have been edited. |
| 304 | * Other check-ins that have been [/help/merge | merged] into the |
| 305 | working checkout but not yet committed. |
| 306 | * Copies of files prior to the most recent undoable operation - needed to |
| 307 | implement the [/help/undo | undo] and [/help/redo | redo] commands. |
| 308 | * The [/help/stash | stash]. |
| 309 | * State information for the [/help/bisect | bisect] command. |
| 310 |
+3
-3
| --- www/webui.wiki | ||
| +++ www/webui.wiki | ||
| @@ -12,13 +12,13 @@ | ||
| 12 | 12 | * Graphs of revision and branching history |
| 13 | 13 | * [./event.wiki | Technical notes] |
| 14 | 14 | * File and version lists and differences |
| 15 | 15 | * Download historical versions as ZIP archives |
| 16 | 16 | * Historical change data |
| 17 | - * Add and remove tags on checkins | |
| 18 | - * Move checkins between branches | |
| 19 | - * Revise checkin comments | |
| 17 | + * Add and remove tags on check-ins | |
| 18 | + * Move check-ins between branches | |
| 19 | + * Revise check-in comments | |
| 20 | 20 | * Manage user credentials and access permissions |
| 21 | 21 | * And so forth... (some [./webpage-ex.md|examples]) |
| 22 | 22 | |
| 23 | 23 | You get all of this, and more, for free when you use Fossil. |
| 24 | 24 | There are no extra programs to install or setup. |
| 25 | 25 |
| --- www/webui.wiki | |
| +++ www/webui.wiki | |
| @@ -12,13 +12,13 @@ | |
| 12 | * Graphs of revision and branching history |
| 13 | * [./event.wiki | Technical notes] |
| 14 | * File and version lists and differences |
| 15 | * Download historical versions as ZIP archives |
| 16 | * Historical change data |
| 17 | * Add and remove tags on checkins |
| 18 | * Move checkins between branches |
| 19 | * Revise checkin comments |
| 20 | * Manage user credentials and access permissions |
| 21 | * And so forth... (some [./webpage-ex.md|examples]) |
| 22 | |
| 23 | You get all of this, and more, for free when you use Fossil. |
| 24 | There are no extra programs to install or setup. |
| 25 |
| --- www/webui.wiki | |
| +++ www/webui.wiki | |
| @@ -12,13 +12,13 @@ | |
| 12 | * Graphs of revision and branching history |
| 13 | * [./event.wiki | Technical notes] |
| 14 | * File and version lists and differences |
| 15 | * Download historical versions as ZIP archives |
| 16 | * Historical change data |
| 17 | * Add and remove tags on check-ins |
| 18 | * Move check-ins between branches |
| 19 | * Revise check-in comments |
| 20 | * Manage user credentials and access permissions |
| 21 | * And so forth... (some [./webpage-ex.md|examples]) |
| 22 | |
| 23 | You get all of this, and more, for free when you use Fossil. |
| 24 | There are no extra programs to install or setup. |
| 25 |