From: Steffen Prohaska <prohaska-wjoc1khpmeg@public.gmane.org>
Date: Mon, 14 Jan 2008 08:29:04 GMT
Subject: Re: safecrlf not in 1.5.4
Message-ID: <E4FD5B11-F61A-4838-B9AD-1E6F6C2B0AD6@zib.de>
In-Reply-To: <7vejcklv84.fsf-jO8aZxhGsIagbBziECNbOZn29agUkmeCHZ5vskTnxNA@public.gmane.org>



On Jan 14, 2008, at 8:30 AM, Junio C Hamano wrote:

>
> Steffen Prohaska <prohaska-wjoc1KHpMeg@public.gmane.org> writes:
>
>> Do you see a chance to have safecrlf in 1.5.4.1?
>
> By definition of 'maint', 1.5.4.X are to fix bugs in the
> features that are in 1.5.4, so the answer is no.

I expected this answer.


> But we could end up having a short cycle for 1.5.5 if we agree
> that the lack of crlf=safe is a severe bug that is worth fixing
> post 1.5.4.
>
> Currently I am not convinced that the lack of crlf=safe is a
> severe and urgent bug worth "fixing" for 1.5.4.  I see it as a
> new feature, a different variant of crlf behaviour we will be
> introducing for audience who are not satisfied with existing the
> crlf variants.


So I should try harder to find better arguments.  But this has
time until the 1.5.4 release is out.  For now, I am being quiet.

(Well, I'll continue to improve the safecrlf patch and most
likely will send it to the list, too.  But I don't expect to find
it anywhere in your repo before 1.5.4.)

	Steffen