doc hash-function-transition: clarify how older gits die on NewHash
Change the "Repository format extension" to accurately describe what happens with different versions of Git when they encounter NewHash repositories, instead of only saying what happens with versions v2.7.0 and later. See ab9cb76f66 ("Repository format version check.", 2005-11-25) and 00a09d57eb ("introduce "extensions" form of core.repositoryformatversion", 2015-06-23) for the relevant changes to the setup code where these variables are checked. Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Ævar Arnfjörð Bjarmason committed
Mar 26, 2018 at 18:27 UTC
45fa195ff0b7a440fae02da1d871f976afa32dff
1 file changed
+8
-3
Documentation/technical/hash-function-transition.txt
+8
-3
@@ -116,10 +116,15 @@ Documentation/technical/repository-version.txt) with extensions
116
objectFormat = newhash
117
compatObjectFormat = sha1
118
119
-Specifying a repository format extension ensures that versions of Git
120
-not aware of NewHash do not try to operate on these repositories,
121
-instead producing an error message:
119
+The combination of setting `core.repositoryFormatVersion=1` and
120
+populating `extensions.*` ensures that all versions of Git later than
121
+`v0.99.9l` will die instead of trying to operate on the NewHash
122
+repository, instead producing an error message.
123
124
+ # Between v0.99.9l and v2.7.0
125
+ $ git status
126
+ fatal: Expected git repo version <= 0, found 1
127
+ # After v2.7.0
128
$ git status
129
fatal: unknown repository extensions found:
130
objectformat