From: Johannes Sixt <j.sixt@viscovery.net>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2011, #13; Mon, 30)
Date: Mon, 30 May 2011 14:19:45 +0200 [thread overview]
Message-ID: <4DE38B61.6030400@viscovery.net> (raw)
In-Reply-To: <BANLkTi=reSnAVgt6k-JaDDu27HP_DEGdhQ@mail.gmail.com>
Am 5/30/2011 14:08, schrieb Ævar Arnfjörð Bjarmason:
> 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.
>
> Johannes, what's the status of that, and is there anything I can do to
> help with that?
I've started with something I thought would be trivial, but I early
tripped over a pitfall where getenv is asked to look for "PATH", and it is
expected to find "Path" when we only have the latter in the environment.
Sigh. I think that's solvable.
Another worry is that the home-grown getenv is not thread-safe. I think it
does not matter today, but who knows...
Anyway, I've at most an hour of quality git time during the week, so it
will take some time...
-- Hannes
next prev parent reply other threads:[~2011-05-30 12:19 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 [this message]
2011-05-30 13:55 ` Ævar Arnfjörð Bjarmason
2011-05-30 18:17 ` Junio C Hamano
2011-05-31 6:06 ` Johannes Sixt
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=4DE38B61.6030400@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).