Clarify two backward incompatible repository options.
It was unclear if the backward compatible features were disabled or the configuration variables that controls them were set to false by default from the description. Obviously we meant the former, but the problem was made worse by the fact that one configuration variable breaks compatibility when set to true and the other one breaks it when set to false. Signed-off-by: Junio C Hamano <junkio@cox.net>
Junio C Hamano committed
Feb 14, 2007 at 01:50 UTC
958545c5a11e5d6745e34df28abdd4a03a1f40fa
1 file changed
+8
-2
Documentation/RelNotes-1.5.0.txt
+8
-2
@@ -25,12 +25,18 @@ Specifically, the available options are:
25
older clients over dumb transports (e.g. http) using older
26
versions of git will also be affected.
27
28
+ To let git use the new loose object format, you have to
29
+ set core.legacyheaders to false.
30
+
31
- Since v1.4.3, configuration repack.usedeltabaseoffset allows
32
packfile to be created in more space efficient format, which
33
cannot be read by git older than that version.
34
32
-The above two are not enabled by default and you explicitly have
33
-to ask for them, because these two features make repositories
35
+ To let git use the new format for packfiles, you have to
36
+ set repack.usedeltabaseoffset to true.
37
+
38
+The above two new features are not enabled by default and you
39
+have explicitly to ask for them, because they make repositories
40
unreadable by older versions of git, and in v1.5.0 we still do
41
not enable them by default for the same reason. We will change
42
this default probably 1 year after 1.4.2's release, when it is