linux-kernel - Re: [ANNOUNCE] GIT 1.5.0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <7vabzht72l.fsf@assigned-by-dhcp.cox.net>
Date:	Wed, 14 Feb 2007 01:35:46 -0800
From:	Junio C Hamano <junkio@....net>
To:	Andy Parkins <andyparkins@...il.com>
Cc:	git@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.5.0

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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/