DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:from:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id;
        b=QBtLHtU40E6ZB+v5Et2De59DvBfqCQ9hzoIt1XJc5d5zOO50gMUYArp/tvQ3R6MT1Oi5v6ly/BQ9PLrlyUoxwjfKcz6xEmBf1Xs9INPCsocRAI8s5ZycnwT4hfmUTIRel4VF8OfDWYFDvr+WsCHAExPlGunmHUMTpWLjIrO+2H8=
From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.5.0
Date: Wed, 14 Feb 2007 09:06:35 +0000
User-Agent: KMail/1.9.5
Cc: Junio C Hamano <junkio@cox.net>, linux-kernel@vger.kernel.org
References: <7vlkj1v3av.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <7vlkj1v3av.fsf@assigned-by-dhcp.cox.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200702140906.37440.andyparkins@gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 709
Lines: 20

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.


Andy
-- 
Dr Andy Parkins, M Eng (hons), MIEE
andyparkins@gmail.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/