Fossil SCM
Typos in fossil-vs-git.wiki are very rare. Grammar mistakes are even rarer.
Commit
3fcd5bd44270c4cc6ee42ae5322bc13b3451bc3251b31a1021e0bac236fb3d3a
Parent
42f2e7a66f1b373…
1 file changed
+1
-1
+1
-1
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -861,11 +861,11 @@ | ||
| 861 | 861 | as this author is aware, but there is now |
| 862 | 862 | [https://lwn.net/ml/git/[email protected]/ |
| 863 | 863 | | a competing SHA-256 based plan] which requires complete repository |
| 864 | 864 | conversion from SHA-1 to SHA-256, breaking all public hashes in the |
| 865 | 865 | repo. One way to characterize such a massive upheaval in Git terms is a |
| 866 | -whole-project rebase, which violates | |
| 866 | +whole-project rebase, which violates the | |
| 867 | 867 | [https://www.atlassian.com/git/tutorials/merging-vs-rebasing#the-golden-rule-of-rebasing|Golden Rule of Rebasing]. |
| 868 | 868 | |
| 869 | 869 | Regardless of the eventual implementation details, we fully expect Git |
| 870 | 870 | to move off SHA-1 eventually and for the changes to take years more to |
| 871 | 871 | percolate through the community. |
| 872 | 872 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -861,11 +861,11 @@ | |
| 861 | as this author is aware, but there is now |
| 862 | [https://lwn.net/ml/git/[email protected]/ |
| 863 | | a competing SHA-256 based plan] which requires complete repository |
| 864 | conversion from SHA-1 to SHA-256, breaking all public hashes in the |
| 865 | repo. One way to characterize such a massive upheaval in Git terms is a |
| 866 | whole-project rebase, which violates |
| 867 | [https://www.atlassian.com/git/tutorials/merging-vs-rebasing#the-golden-rule-of-rebasing|Golden Rule of Rebasing]. |
| 868 | |
| 869 | Regardless of the eventual implementation details, we fully expect Git |
| 870 | to move off SHA-1 eventually and for the changes to take years more to |
| 871 | percolate through the community. |
| 872 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -861,11 +861,11 @@ | |
| 861 | as this author is aware, but there is now |
| 862 | [https://lwn.net/ml/git/[email protected]/ |
| 863 | | a competing SHA-256 based plan] which requires complete repository |
| 864 | conversion from SHA-1 to SHA-256, breaking all public hashes in the |
| 865 | repo. One way to characterize such a massive upheaval in Git terms is a |
| 866 | whole-project rebase, which violates the |
| 867 | [https://www.atlassian.com/git/tutorials/merging-vs-rebasing#the-golden-rule-of-rebasing|Golden Rule of Rebasing]. |
| 868 | |
| 869 | Regardless of the eventual implementation details, we fully expect Git |
| 870 | to move off SHA-1 eventually and for the changes to take years more to |
| 871 | percolate through the community. |
| 872 |