Fossil SCM
Small tweaks to the gitusers doc
Commit
3bfae2309cd2990298bfd5b289468c50c780ee4f28f0f6e32a7e251a3a50ed2b
Parent
03bb48a3b95b336…
1 file changed
+3
-3
+3
-3
| --- www/gitusers.md | ||
| +++ www/gitusers.md | ||
| @@ -281,11 +281,11 @@ | ||
| 281 | 281 | [server]: /help?cmd=server |
| 282 | 282 | [stash]: /help?cmd=stash |
| 283 | 283 | [undo]: /help?cmd=undo |
| 284 | 284 | |
| 285 | 285 | |
| 286 | -## <a id="log"></a> Fossil’s Timeline Is The “Log” | |
| 286 | +## <a id="log"></a> Fossil’s Timeline Is the “Log” | |
| 287 | 287 | |
| 288 | 288 | Git users often need to use the `git log` command to dig linearly through |
| 289 | 289 | commit histories due to its [weak data model][wdm], giving [O(n) |
| 290 | 290 | performance][ocomp]. |
| 291 | 291 | |
| @@ -442,11 +442,11 @@ | ||
| 442 | 442 | of commit comments is not enforced or obeyed by default in Fossil. |
| 443 | 443 | However, there is a setting under Admin → Timeline → “Truncate comment |
| 444 | 444 | at first blank line (Git-style)” to change this for `/timeline` |
| 445 | 445 | displays. Alternately, you could enable the “Allow block-markup in |
| 446 | 446 | timeline” setting under Admin → Timeline, then apply [local skin |
| 447 | -customizations][cskin] to put that first comment in in bold or whatever | |
| 447 | +customizations][cskin] to put that first comment in bold or whatever | |
| 448 | 448 | suits. |
| 449 | 449 | |
| 450 | 450 | Because this isn’t a typical Fossil convention, you’re likely to find |
| 451 | 451 | other odd differences between it and Git-based infrastructure. For |
| 452 | 452 | instance, Vim doesn’t ship with syntax support for Fossil commit |
| @@ -728,11 +728,11 @@ | ||
| 728 | 728 | artifacts. Bob’s first command doesn’t delete anything, merely tells |
| 729 | 729 | Fossil to hide his mistake from timeline views by inserting a few new |
| 730 | 730 | records into the local repository to change how the client interprets |
| 731 | 731 | the data it finds there henceforth.(^One to change the tag marking this |
| 732 | 732 | commit’s branch name to “`MISTAKE`,” one to mark that branch as hidden, |
| 733 | -and one to close it to further commits.). | |
| 733 | +and one to close it to further commits.) | |
| 734 | 734 | |
| 735 | 735 | Bob’s second command switches his working directory back to the prior |
| 736 | 736 | commit on that branch. We’re presuming it was “`trunk`” for the sake of |
| 737 | 737 | the example, but it works for any parent branch name. The command works |
| 738 | 738 | because the name “`trunk`” now means something different to Fossil by |
| 739 | 739 |
| --- www/gitusers.md | |
| +++ www/gitusers.md | |
| @@ -281,11 +281,11 @@ | |
| 281 | [server]: /help?cmd=server |
| 282 | [stash]: /help?cmd=stash |
| 283 | [undo]: /help?cmd=undo |
| 284 | |
| 285 | |
| 286 | ## <a id="log"></a> Fossil’s Timeline Is The “Log” |
| 287 | |
| 288 | Git users often need to use the `git log` command to dig linearly through |
| 289 | commit histories due to its [weak data model][wdm], giving [O(n) |
| 290 | performance][ocomp]. |
| 291 | |
| @@ -442,11 +442,11 @@ | |
| 442 | of commit comments is not enforced or obeyed by default in Fossil. |
| 443 | However, there is a setting under Admin → Timeline → “Truncate comment |
| 444 | at first blank line (Git-style)” to change this for `/timeline` |
| 445 | displays. Alternately, you could enable the “Allow block-markup in |
| 446 | timeline” setting under Admin → Timeline, then apply [local skin |
| 447 | customizations][cskin] to put that first comment in in bold or whatever |
| 448 | suits. |
| 449 | |
| 450 | Because this isn’t a typical Fossil convention, you’re likely to find |
| 451 | other odd differences between it and Git-based infrastructure. For |
| 452 | instance, Vim doesn’t ship with syntax support for Fossil commit |
| @@ -728,11 +728,11 @@ | |
| 728 | artifacts. Bob’s first command doesn’t delete anything, merely tells |
| 729 | Fossil to hide his mistake from timeline views by inserting a few new |
| 730 | records into the local repository to change how the client interprets |
| 731 | the data it finds there henceforth.(^One to change the tag marking this |
| 732 | commit’s branch name to “`MISTAKE`,” one to mark that branch as hidden, |
| 733 | and one to close it to further commits.). |
| 734 | |
| 735 | Bob’s second command switches his working directory back to the prior |
| 736 | commit on that branch. We’re presuming it was “`trunk`” for the sake of |
| 737 | the example, but it works for any parent branch name. The command works |
| 738 | because the name “`trunk`” now means something different to Fossil by |
| 739 |
| --- www/gitusers.md | |
| +++ www/gitusers.md | |
| @@ -281,11 +281,11 @@ | |
| 281 | [server]: /help?cmd=server |
| 282 | [stash]: /help?cmd=stash |
| 283 | [undo]: /help?cmd=undo |
| 284 | |
| 285 | |
| 286 | ## <a id="log"></a> Fossil’s Timeline Is the “Log” |
| 287 | |
| 288 | Git users often need to use the `git log` command to dig linearly through |
| 289 | commit histories due to its [weak data model][wdm], giving [O(n) |
| 290 | performance][ocomp]. |
| 291 | |
| @@ -442,11 +442,11 @@ | |
| 442 | of commit comments is not enforced or obeyed by default in Fossil. |
| 443 | However, there is a setting under Admin → Timeline → “Truncate comment |
| 444 | at first blank line (Git-style)” to change this for `/timeline` |
| 445 | displays. Alternately, you could enable the “Allow block-markup in |
| 446 | timeline” setting under Admin → Timeline, then apply [local skin |
| 447 | customizations][cskin] to put that first comment in bold or whatever |
| 448 | suits. |
| 449 | |
| 450 | Because this isn’t a typical Fossil convention, you’re likely to find |
| 451 | other odd differences between it and Git-based infrastructure. For |
| 452 | instance, Vim doesn’t ship with syntax support for Fossil commit |
| @@ -728,11 +728,11 @@ | |
| 728 | artifacts. Bob’s first command doesn’t delete anything, merely tells |
| 729 | Fossil to hide his mistake from timeline views by inserting a few new |
| 730 | records into the local repository to change how the client interprets |
| 731 | the data it finds there henceforth.(^One to change the tag marking this |
| 732 | commit’s branch name to “`MISTAKE`,” one to mark that branch as hidden, |
| 733 | and one to close it to further commits.) |
| 734 | |
| 735 | Bob’s second command switches his working directory back to the prior |
| 736 | commit on that branch. We’re presuming it was “`trunk`” for the sake of |
| 737 | the example, but it works for any parent branch name. The command works |
| 738 | because the name “`trunk`” now means something different to Fossil by |
| 739 |