Fossil SCM
Fix broken link in fossil-v-git.
Commit
fd903e92c2187d3613f5f0e2df7862273ebdebe42c296ba7ce1c1cc4b54ede13
Parent
5522ad5fa42bf05…
1 file changed
+1
-2
+1
-2
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -862,12 +862,11 @@ | ||
| 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 | 866 | whole-project rebase, which violates |
| 867 | -[https://blog.axosoft.com/golden-rule-of-rebasing-in-git/ | Git's own | |
| 868 | -Golden Rule of Rebasing]. | |
| 867 | +[https://www.atlassian.com/git/tutorials/merging-vs-rebasing#the-golden-rule-of-rebasing|Golden Rule of Rebasing]. | |
| 869 | 868 | |
| 870 | 869 | Regardless of the eventual implementation details, we fully expect Git |
| 871 | 870 | to move off SHA-1 eventually and for the changes to take years more to |
| 872 | 871 | percolate through the community. |
| 873 | 872 | |
| 874 | 873 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -862,12 +862,11 @@ | |
| 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://blog.axosoft.com/golden-rule-of-rebasing-in-git/ | Git's own |
| 868 | Golden Rule of Rebasing]. |
| 869 | |
| 870 | Regardless of the eventual implementation details, we fully expect Git |
| 871 | to move off SHA-1 eventually and for the changes to take years more to |
| 872 | percolate through the community. |
| 873 | |
| 874 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -862,12 +862,11 @@ | |
| 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 | |
| 873 |