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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am 5/30/2011 20:17, schrieb Junio C Hamano:
> Ãvar ArnfjÃrà Bjarmason <avarab@xxxxxxxxx> writes:
> 
>> On Mon, May 30, 2011 at 10:16, Junio C Hamano <gitster@xxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]