Re: What's cooking in git.git (May 2011, #13; Mon, 30)

From: Johannes Sixt <j.sixt@viscovery.net>
Date: May 31, 2011, 06:06 UTC
Message-ID: <4DE4857A.70605@viscovery.net>
In-Reply-To: <7vsjrwm4sj.fsf@alter.siamese.dyndns.org>

Am 5/30/2011 20:17, schrieb Junio C Hamano:

Show 15 quoted lines

> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> 
>> On Mon, May 30, 2011 at 10:16, Junio C Hamano <gitster@pobox.com> wrote:
>>
>>> * ab/i18n-scripts (2011-05-21) 48 commits
>>>  (merged to 'next' on 2011-05-23 at 69164a3)
>>> [...]
>>> Rerolled.
>>> Will cook a bit longer.
>>
>> This being ready for master is waiting on Johannes Sixt's patches to
>> supply a fallback getenv() on Win32.
> 
> That getenv thing by itself is actually a non blocker for git.git itself,
> as mingw folks fork from my "next" anyway, I think.

Things are not that simple. I think there are (a few) Windows people, including myself, who follow master[*] and do not depend on an msysgit release. But as far as I am concerned, I do not mind backing out changes that break on Windows until a solution is found.

[*] I do include cooking topics where I think that there is a chance that they break on Windows.

-- Hannes