Fossil SCM
Added another link from www/fossil-v-git.wiki to rebaseharm.md.
Commit
29997f803b4c14c4bf24bff86cc1b795aea832293903e56c027bc4bf9ba29094
Parent
b4aadf2cea1a4a0…
1 file changed
+4
-1
+4
-1
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -572,11 +572,11 @@ | ||
| 572 | 572 | mistakes. |
| 573 | 573 | |
| 574 | 574 | Fossil, in contrast, puts more emphasis on recording exactly what happened, |
| 575 | 575 | including all of the messy errors, dead-ends, experimental branches, and |
| 576 | 576 | so forth. One might argue that this |
| 577 | -makes the history of a Fossil project "messy." But another point of view | |
| 577 | +makes the history of a Fossil project "messy," but another point of view | |
| 578 | 578 | is that this makes the history "accurate." In actual practice, the |
| 579 | 579 | superior reporting tools available in Fossil mean that the added "mess" |
| 580 | 580 | is not a factor. |
| 581 | 581 | |
| 582 | 582 | Like Git, Fossil has an [/help?cmd=amend|amend command] for modifying |
| @@ -588,10 +588,13 @@ | ||
| 588 | 588 | [/doc/trunk/www/shunning.wiki|shunning mechanism], but it has strict |
| 589 | 589 | limitations that prevent global history rewrites. |
| 590 | 590 | |
| 591 | 591 | One commentator characterized Git as recording history according to |
| 592 | 592 | the victors, whereas Fossil records history as it actually happened. |
| 593 | + | |
| 594 | +We go into more detail on this topic in a separate article, | |
| 595 | +[./rebaseharm.md | Rebase Considered Harmful]. | |
| 593 | 596 | |
| 594 | 597 | |
| 595 | 598 | <h3 id="hash">2.8 Hash Algorithm: SHA-3 vs SHA-2 vs SHA-1</h3> |
| 596 | 599 | |
| 597 | 600 | Fossil started out using 160-bit SHA-1 hashes to identify check-ins, |
| 598 | 601 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -572,11 +572,11 @@ | |
| 572 | mistakes. |
| 573 | |
| 574 | Fossil, in contrast, puts more emphasis on recording exactly what happened, |
| 575 | including all of the messy errors, dead-ends, experimental branches, and |
| 576 | so forth. One might argue that this |
| 577 | makes the history of a Fossil project "messy." But another point of view |
| 578 | is that this makes the history "accurate." In actual practice, the |
| 579 | superior reporting tools available in Fossil mean that the added "mess" |
| 580 | is not a factor. |
| 581 | |
| 582 | Like Git, Fossil has an [/help?cmd=amend|amend command] for modifying |
| @@ -588,10 +588,13 @@ | |
| 588 | [/doc/trunk/www/shunning.wiki|shunning mechanism], but it has strict |
| 589 | limitations that prevent global history rewrites. |
| 590 | |
| 591 | One commentator characterized Git as recording history according to |
| 592 | the victors, whereas Fossil records history as it actually happened. |
| 593 | |
| 594 | |
| 595 | <h3 id="hash">2.8 Hash Algorithm: SHA-3 vs SHA-2 vs SHA-1</h3> |
| 596 | |
| 597 | Fossil started out using 160-bit SHA-1 hashes to identify check-ins, |
| 598 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -572,11 +572,11 @@ | |
| 572 | mistakes. |
| 573 | |
| 574 | Fossil, in contrast, puts more emphasis on recording exactly what happened, |
| 575 | including all of the messy errors, dead-ends, experimental branches, and |
| 576 | so forth. One might argue that this |
| 577 | makes the history of a Fossil project "messy," but another point of view |
| 578 | is that this makes the history "accurate." In actual practice, the |
| 579 | superior reporting tools available in Fossil mean that the added "mess" |
| 580 | is not a factor. |
| 581 | |
| 582 | Like Git, Fossil has an [/help?cmd=amend|amend command] for modifying |
| @@ -588,10 +588,13 @@ | |
| 588 | [/doc/trunk/www/shunning.wiki|shunning mechanism], but it has strict |
| 589 | limitations that prevent global history rewrites. |
| 590 | |
| 591 | One commentator characterized Git as recording history according to |
| 592 | the victors, whereas Fossil records history as it actually happened. |
| 593 | |
| 594 | We go into more detail on this topic in a separate article, |
| 595 | [./rebaseharm.md | Rebase Considered Harmful]. |
| 596 | |
| 597 | |
| 598 | <h3 id="hash">2.8 Hash Algorithm: SHA-3 vs SHA-2 vs SHA-1</h3> |
| 599 | |
| 600 | Fossil started out using 160-bit SHA-1 hashes to identify check-ins, |
| 601 |