LKML Archive on
help / color / mirror / Atom feed
From: Junio C Hamano <>
To: Andy Parkins <>
Subject: Re: [ANNOUNCE] GIT 1.5.0
Date: Wed, 14 Feb 2007 01:48:28 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Junio C. Hamano's message of "Wed, 14 Feb 2007 01:35:46 -0800")

Junio C Hamano <> writes:

> Andy Parkins <> writes:
>> On Wednesday 2007 February 14 03:14, Junio C Hamano wrote:
>>>  - There is a configuration variable core.legacyheaders that
>>> The above two are not enabled by default and you explicitly have
>>> to ask for them, because these two features make repositories
>> It isn't really the case that you have to _enable_ legacyheaders?  It defaults 
>> to on already.  You actually have to disable legacyheaders.
> Ah, true.  What it should have stressed is that we currently
> default to the safer, backward compatible behaviour, and you have
> to explicitly ask to use more efficient but incompatible
> encoding by setting core.legacyheaders to false.

So this will be the updated explanation.

-- >8 --
diff --git a/Documentation/RelNotes-1.5.0.txt b/Documentation/RelNotes-1.5.0.txt
index f0120e1..0989ded 100644
--- a/Documentation/RelNotes-1.5.0.txt
+++ b/Documentation/RelNotes-1.5.0.txt
@@ -25,12 +25,18 @@ Specifically, the available options are:
    older clients over dumb transports (e.g. http) using older
    versions of git will also be affected.
+   To let git use the new loose object format, you have to
+   set core.legacyheaders to false.
  - Since v1.4.3, configuration repack.usedeltabaseoffset allows
    packfile to be created in more space efficient format, which
    cannot be read by git older than that version.
-The above two are not enabled by default and you explicitly have
-to ask for them, because these two features make repositories
+   To let git use the new format for packfiles, you have to
+   set repack.usedeltabaseoffset to true.
+The above two new features are not enabled by default and you
+have explicitly to ask for them, because they make repositories
 unreadable by older versions of git, and in v1.5.0 we still do
 not enable them by default for the same reason.  We will change
 this default probably 1 year after 1.4.2's release, when it is

  reply	other threads:[~2007-02-14  9:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14  3:14 Junio C Hamano
2007-02-14  9:06 ` Andy Parkins
2007-02-14  9:35   ` Junio C Hamano
2007-02-14  9:48     ` Junio C Hamano [this message]
2007-02-14 14:57 ` Bill Lear
2007-02-14 16:45   ` Linus Torvalds
2007-02-15  1:55 ` Jakub Narebski
2007-02-15  2:11   ` Shawn O. Pearce

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: [ANNOUNCE] GIT 1.5.0' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).