core.legacyheaders: Use the description used in RelNotes-1.5.0
PATCH v2 1/1 core.legacyheaders: Use the description used in RelNotes-1.5.0
It explains what it does and why, and says how to use the new format.
Signed-off-by Santi Béjar <[email protected]>
---
Hi *,
this version removes one of the "older clients".
Documentation/config.txt | 15 +++++++++++---- 1 files changed, 11 insertions(+), 4 deletions(-)
Documentation/config.txt +11 -4
@@ -192,10 +192,17 @@ core.compression:: slowest. core.legacyheaders:: - A boolean which enables the legacy object header format in case - you want to interoperate with old clients accessing the object - database directly (where the "http://" and "rsync://" protocols - count as direct access). + A boolean which + changes the format of loose objects so that they are more + efficient to pack and to send out of the repository over git + native protocol, since v1.4.2. However, loose objects + written in the new format cannot be read by git older than + that version; people fetching from your repository using + older clients over dumb transports (e.g. http) will also + be affected. ++ +To let git use the new loose object format, you have to +set core.legacyheaders to false. core.packedGitWindowSize:: Number of bytes of a pack file to map into memory in a
Signature · 1 line
1.5.0.1.576.g78541
Documentation/config.txt core.compression:: · line 195
Quoted 3 lines · On Saturday, February 24, 2007 at 10:17:10 (+0100)…
...
core.legacyheaders::Documentation/config.txt +1
-0+ A boolean which
Since others have often worried about "proper" English --- strictly speaking the above should be:
"A boolean that..."
Bill