Fossil SCM
(Grammar) hashpolicy.wiki change.
Commit
fbd7d8d9630d21b49e067db3ca5421fced478527b3393889eecf7e1aa8cccb3c
Parent
d1788d563438434…
1 file changed
+1
-1
+1
-1
| --- www/hashpolicy.wiki | ||
| +++ www/hashpolicy.wiki | ||
| @@ -78,11 +78,11 @@ | ||
| 78 | 78 | Version 2.0 extended the [./fileformat.wiki|Fossil file format] |
| 79 | 79 | to allow artifacts to be named by either SHA1 or SHA3-256 hashes. |
| 80 | 80 | (SHA3-256 is the only variant of SHA3 that |
| 81 | 81 | Fossil uses for artifact naming, so for the remainder of this article |
| 82 | 82 | it will be called simply "SHA3". Similarly, "Hardened SHA1" will |
| 83 | -shortened to "SHA1" in the remaining text.) | |
| 83 | +be shortened to "SHA1" in the remaining text.) | |
| 84 | 84 | |
| 85 | 85 | To be clear: Fossil (version 2.0 and later) |
| 86 | 86 | allows the SHA1 and SHA3 hashes to be mixed within |
| 87 | 87 | the same repository. Older check-ins, created years ago, |
| 88 | 88 | continue to be named using their legacy SHA1 hashes while |
| 89 | 89 |
| --- www/hashpolicy.wiki | |
| +++ www/hashpolicy.wiki | |
| @@ -78,11 +78,11 @@ | |
| 78 | Version 2.0 extended the [./fileformat.wiki|Fossil file format] |
| 79 | to allow artifacts to be named by either SHA1 or SHA3-256 hashes. |
| 80 | (SHA3-256 is the only variant of SHA3 that |
| 81 | Fossil uses for artifact naming, so for the remainder of this article |
| 82 | it will be called simply "SHA3". Similarly, "Hardened SHA1" will |
| 83 | shortened to "SHA1" in the remaining text.) |
| 84 | |
| 85 | To be clear: Fossil (version 2.0 and later) |
| 86 | allows the SHA1 and SHA3 hashes to be mixed within |
| 87 | the same repository. Older check-ins, created years ago, |
| 88 | continue to be named using their legacy SHA1 hashes while |
| 89 |
| --- www/hashpolicy.wiki | |
| +++ www/hashpolicy.wiki | |
| @@ -78,11 +78,11 @@ | |
| 78 | Version 2.0 extended the [./fileformat.wiki|Fossil file format] |
| 79 | to allow artifacts to be named by either SHA1 or SHA3-256 hashes. |
| 80 | (SHA3-256 is the only variant of SHA3 that |
| 81 | Fossil uses for artifact naming, so for the remainder of this article |
| 82 | it will be called simply "SHA3". Similarly, "Hardened SHA1" will |
| 83 | be shortened to "SHA1" in the remaining text.) |
| 84 | |
| 85 | To be clear: Fossil (version 2.0 and later) |
| 86 | allows the SHA1 and SHA3 hashes to be mixed within |
| 87 | the same repository. Older check-ins, created years ago, |
| 88 | continue to be named using their legacy SHA1 hashes while |
| 89 |