Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Added another link from www/fossil-v-git.wiki to rebaseharm.md. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
29997f803b4c14c4bf24bff86cc1b795 |
| User & Date: | wyoung 2019-09-13 09:00:06 |
Context
|
2019-09-13
| ||
| 09:23 | Assorted grammar and spelling fixes in www/rebaseharm.md. Also added named anchors to all of the sections. check-in: cd689b3813 user: wyoung tags: trunk | |
| 09:00 | Added another link from www/fossil-v-git.wiki to rebaseharm.md. check-in: 29997f803b user: wyoung tags: trunk | |
|
2019-09-12
| ||
| 17:51 | Add the optimized file_is_simple_pathname_nonstrict() as an alternative to file_is_simple_pathname() when parsing manifests. check-in: b4aadf2cea user: drh tags: trunk | |
Changes
Changes to www/fossil-v-git.wiki.
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
...
586
587
588
589
590
591
592
593
594
595
596
597
598
599
|
it appear as if development had been linear. Git strives to record what the development of a project should have looked like had there been no mistakes. Fossil, in contrast, puts more emphasis on recording exactly what happened, including all of the messy errors, dead-ends, experimental branches, and so forth. One might argue that this makes the history of a Fossil project "messy." But another point of view is that this makes the history "accurate." In actual practice, the superior reporting tools available in Fossil mean that the added "mess" is not a factor. Like Git, Fossil has an [/help?cmd=amend|amend command] for modifying prior commits, but unlike in Git, this works not by replacing data in the repository, but by adding a correction record to the repository that ................................................................................ information is still there in the repository, it is just overridden from the amendment point forward. For extreme situations, Fossil adds the [/doc/trunk/www/shunning.wiki|shunning mechanism], but it has strict limitations that prevent global history rewrites. One commentator characterized Git as recording history according to the victors, whereas Fossil records history as it actually happened. <h3 id="hash">2.8 Hash Algorithm: SHA-3 vs SHA-2 vs SHA-1</h3> Fossil started out using 160-bit SHA-1 hashes to identify check-ins, just as in Git. That changed in early 2017 when news of the [https://shattered.io/|SHAttered attack] broke, demonstrating that SHA-1 |
|
>
>
>
|
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
...
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
|
it appear as if development had been linear. Git strives to record what the development of a project should have looked like had there been no mistakes. Fossil, in contrast, puts more emphasis on recording exactly what happened, including all of the messy errors, dead-ends, experimental branches, and so forth. One might argue that this makes the history of a Fossil project "messy," but another point of view is that this makes the history "accurate." In actual practice, the superior reporting tools available in Fossil mean that the added "mess" is not a factor. Like Git, Fossil has an [/help?cmd=amend|amend command] for modifying prior commits, but unlike in Git, this works not by replacing data in the repository, but by adding a correction record to the repository that ................................................................................ information is still there in the repository, it is just overridden from the amendment point forward. For extreme situations, Fossil adds the [/doc/trunk/www/shunning.wiki|shunning mechanism], but it has strict limitations that prevent global history rewrites. One commentator characterized Git as recording history according to the victors, whereas Fossil records history as it actually happened. We go into more detail on this topic in a separate article, [./rebaseharm.md | Rebase Considered Harmful]. <h3 id="hash">2.8 Hash Algorithm: SHA-3 vs SHA-2 vs SHA-1</h3> Fossil started out using 160-bit SHA-1 hashes to identify check-ins, just as in Git. That changed in early 2017 when news of the [https://shattered.io/|SHAttered attack] broke, demonstrating that SHA-1 |