Documentation/RelNotes-1.6.0.txt: Expand on the incompatible packfiles
PATCH 1/1 Documentation/RelNotes-1.6.0.txt: Expand on the incompatible packfiles
Note that v1.4.4.5 supports pack index v2, and describe how to keep your repositories backwards-compatible, shall you need to.
---
Documentation/RelNotes-1.6.0.txt | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-)
Documentation/RelNotes-1.6.0.txt +3 -1
@@ -21,7 +21,9 @@ main git.git codebase. By default, packfiles created with this version uses delta-base-offset encoding introduced in v1.4.4. Pack idx files are using version 2 that allows larger packs and added robustness thanks to its CRC checking, -introduced in v1.5.2. +introduced in v1.5.2 and v1.4.4.5. If you want to keep your repositories +backwards compatible past these versions, set repack.useDeltaBaseOffset +to false or pack.indexVersion to 1, respectively. GIT_CONFIG, which was only documented as affecting "git config", but actually affected all git commands, now only affects "git config".
Documentation/RelNotes-1.6.0.txt main git.git codebase. · line 26
Quoted 3 lines · Petr Baudis
Documentation/RelNotes-1.6.0.txt +3
-0+introduced in v1.5.2 and v1.4.4.5. If you want to keep your repositories +backwards compatible past these versions, set repack.useDeltaBaseOffset +to false or pack.indexVersion to 1, respectively.
'or'? Not 'and'?
You shouldn't have, I think, this "respectively" here. You need it only if you are writing "a, b, c, then a', b', c', respectively".
Signature · 3 lines
Jakub Narebski Warsaw, Poland ShadeHawk on #git
Quoted 10 lines · Jakub Narebski
Documentation/RelNotes-1.6.0.txt main git.git codebase. · line 26
Quoted 3 lines · Petr Baudis
Documentation/RelNotes-1.6.0.txt +3
-0+introduced in v1.5.2 and v1.4.4.5. If you want to keep your repositories +backwards compatible past these versions, set repack.useDeltaBaseOffset +to false or pack.indexVersion to 1, respectively.'or'? Not 'and'?
You shouldn't have, I think, this "respectively" here. You need it only if you are writing "a, b, c, then a', b', c', respectively".
The "respectively" means that the two options relate each to one of the two new features. I'm unclear about the 'or'-'and' question, though.
Petr "Pasky" Baudis
Quoted 9 lines · Petr Baudis
Quoted 8 lines · Jakub Narebski
Documentation/RelNotes-1.6.0.txt main git.git codebase. · line 26
Quoted 3 lines · Petr Baudis
Documentation/RelNotes-1.6.0.txt +3
-0+introduced in v1.5.2 and v1.4.4.5. If you want to keep your repositories +backwards compatible past these versions, set repack.useDeltaBaseOffset +to false or pack.indexVersion to 1, respectively.'or'? Not 'and'?
Quoted 5 lines
Quoted 2 lines
You shouldn't have, I think, this "respectively" here. You need it only if you are writing "a, b, c, then a', b', c', respectively".
The "respectively" means that the two options relate each to one of the two new features.
Sorry, I have forgot that "respectively" might refer to the context which I don't see in a patch.
Quoted 1 line
I'm unclear about the 'or'-'and' question, though.
If you want to be backwards compatibile with pre v1.4.4.5 clients, do you have to set either option, or both options, or what? The same with pre v1.5.2 client...
Signature · 2 lines
Jakub Narebski Poland
Quoted 6 lines · Jakub Narebski
Quoted 1 line · Petr Baudis
I'm unclear about the 'or'-'and' question, though.
If you want to be backwards compatibile with pre v1.4.4.5 clients, do you have to set either option, or both options, or what? The same with pre v1.5.2 client...
If you want to be backwards compatible with _either_ pre-v1.4.4 or pre-v1.5.2, you will set _either_ (a) or (b). Setting (a) implies you want to set (b) too, though. :-)
Petr "Pasky" Baudis