From: Johannes Sixt <j.sixt@viscovery.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2011, #13; Mon, 30)
Date: Tue, 31 May 2011 08:06:50 +0200 [thread overview]
Message-ID: <4DE4857A.70605@viscovery.net> (raw)
In-Reply-To: <7vsjrwm4sj.fsf@alter.siamese.dyndns.org>
Am 5/30/2011 20:17, schrieb Junio C Hamano:
> Æ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
next prev parent reply other threads:[~2011-05-31 6:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 8:16 What's cooking in git.git (May 2011, #13; Mon, 30) Junio C Hamano
2011-05-30 12:08 ` Ævar Arnfjörð Bjarmason
2011-05-30 12:19 ` Johannes Sixt
2011-05-30 13:55 ` Ævar Arnfjörð Bjarmason
2011-05-30 18:17 ` Junio C Hamano
2011-05-31 6:06 ` Johannes Sixt [this message]
2011-05-31 6:21 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DE4857A.70605@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.