Fossil SCM
Reworked the final paragraph of the new section 2.8 in fossil-v-git.wiki, adding in a mention of www/branching.wiki to the comparison, to make it fairer.
Commit
8f7576b0242accf6e0aae1e03debd89a7bcc01e4ee3ccbe559fbf85c0a727dbb
Parent
c71fe99f9b21b0b…
1 file changed
+9
-5
+9
-5
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -670,15 +670,19 @@ | ||
| 670 | 670 | that Fossil's command interface is simpler than Git's: there are fewer |
| 671 | 671 | concepts to keep track of in your mental model of Fossil's internal |
| 672 | 672 | operation. |
| 673 | 673 | |
| 674 | 674 | Fossil's implementation of the feature is also simpler to describe. The |
| 675 | -online help for <tt> [/help?cmd=merge | fossil merge]</tt> is currently | |
| 676 | -41 lines long, whereas the aggregate man page length for the above three | |
| 677 | -Git commands is over 1000 lines, much of it mutually redundant. (e.g. | |
| 678 | -the <tt>--edit</tt> and <tt>--no-commit</tt> options get described three | |
| 679 | -different times, each time differently.) | |
| 675 | +brief online help for <tt>[/help?cmd=merge | fossil merge]</tt> is | |
| 676 | +currently 41 lines long, to which you want to add the 600 lines of | |
| 677 | +[./branching.wiki | the branching document]. The equivalent | |
| 678 | +documentation in Git is the aggregation of the man pages for the above | |
| 679 | +three commands, which is over 1000 lines, much of it mutually redundant. | |
| 680 | +(e.g. the <tt>--edit</tt> and <tt>--no-commit</tt> options get | |
| 681 | +described three different times, each time differently.) Fossil's | |
| 682 | +documentation is not only more concise, it gives a nice split of brief | |
| 683 | +online help and full online documentation. | |
| 680 | 684 | |
| 681 | 685 | |
| 682 | 686 | <h3 id="hash">2.9 Hash Algorithm: SHA-3 vs SHA-2 vs SHA-1</h3> |
| 683 | 687 | |
| 684 | 688 | Fossil started out using 160-bit SHA-1 hashes to identify check-ins, |
| 685 | 689 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -670,15 +670,19 @@ | |
| 670 | that Fossil's command interface is simpler than Git's: there are fewer |
| 671 | concepts to keep track of in your mental model of Fossil's internal |
| 672 | operation. |
| 673 | |
| 674 | Fossil's implementation of the feature is also simpler to describe. The |
| 675 | online help for <tt> [/help?cmd=merge | fossil merge]</tt> is currently |
| 676 | 41 lines long, whereas the aggregate man page length for the above three |
| 677 | Git commands is over 1000 lines, much of it mutually redundant. (e.g. |
| 678 | the <tt>--edit</tt> and <tt>--no-commit</tt> options get described three |
| 679 | different times, each time differently.) |
| 680 | |
| 681 | |
| 682 | <h3 id="hash">2.9 Hash Algorithm: SHA-3 vs SHA-2 vs SHA-1</h3> |
| 683 | |
| 684 | Fossil started out using 160-bit SHA-1 hashes to identify check-ins, |
| 685 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -670,15 +670,19 @@ | |
| 670 | that Fossil's command interface is simpler than Git's: there are fewer |
| 671 | concepts to keep track of in your mental model of Fossil's internal |
| 672 | operation. |
| 673 | |
| 674 | Fossil's implementation of the feature is also simpler to describe. The |
| 675 | brief online help for <tt>[/help?cmd=merge | fossil merge]</tt> is |
| 676 | currently 41 lines long, to which you want to add the 600 lines of |
| 677 | [./branching.wiki | the branching document]. The equivalent |
| 678 | documentation in Git is the aggregation of the man pages for the above |
| 679 | three commands, which is over 1000 lines, much of it mutually redundant. |
| 680 | (e.g. the <tt>--edit</tt> and <tt>--no-commit</tt> options get |
| 681 | described three different times, each time differently.) Fossil's |
| 682 | documentation is not only more concise, it gives a nice split of brief |
| 683 | online help and full online documentation. |
| 684 | |
| 685 | |
| 686 | <h3 id="hash">2.9 Hash Algorithm: SHA-3 vs SHA-2 vs SHA-1</h3> |
| 687 | |
| 688 | Fossil started out using 160-bit SHA-1 hashes to identify check-ins, |
| 689 |