Re: What's cooking in git.git (Jul 2013, #09; Mon, 29)

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 1, 2013, 21:12 UTC
Message-ID: <7vtxj9qfnm.fsf@alter.siamese.dyndns.org>
In-Reply-To: <51FACA67.8090207@ramsay1.demon.co.uk>

Ramsay Jones <ramsay@ramsay1.demon.co.uk> writes:

Show 18 quoted lines

> Junio C Hamano wrote:
>> Ramsay Jones <ramsay@ramsay1.demon.co.uk> writes:
>> 
>>>>  I am personally in favor of this simpler solution.  Comments?
>>>
>>> I had expected this to me marked for 'master'.
>>>
>>> Has this simply been overlooked, or do you have reservations about
>>> applying this patch?
>> 
>> I am just being careful and do want to keep it cooking in 'next'
>> during the feature freeze.  The more users work with 'next' (not
>> "work *on* 'next'"), the more confidence we would be with, and
>> hopefully this can be one of the topis that graduate early after
>> the 1.8.4 release.
>
> Hmm, this patch is a bug-fix for a bug that (currently) will be
> _introduced_ by v1.8.4.

OK, let's merge it then.  Thanks for being patient with me.

> Do you want me to try and find a different bug-fix for v1.8.4?
> (Although that would most likely be more risky than simply taking
> this patch! ;-) ).

Absolutely not, and I 100% agree with you.