git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.5.0
Date: Wed, 14 Feb 2007 01:35:46 -0800	[thread overview]
Message-ID: <7vabzht72l.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200702140906.37440.andyparkins@gmail.com> (Andy Parkins's message of "Wed, 14 Feb 2007 09:06:35 +0000")

Andy Parkins <andyparkins@gmail.com> 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.

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

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14  3:14 [ANNOUNCE] GIT 1.5.0 Junio C Hamano
2007-02-14  9:06 ` Andy Parkins
2007-02-14  9:35   ` Junio C Hamano [this message]
2007-02-14  9:48     ` Junio C Hamano
2007-02-14 12:42 ` Matthieu Moy
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
2007-02-16 22:31 ` A note from the maintainer Junio C Hamano
2007-02-17  2:35   ` Johannes Schindelin
2007-02-23  6:03     ` Junio C Hamano

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=7vabzht72l.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=andyparkins@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).