From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2011, #11; Tue, 24)
Date: Wed, 25 May 2011 11:36:13 +0200 [thread overview]
Message-ID: <BANLkTi=5koa_f_xqaGvKPrEnKMh7ziOT0g@mail.gmail.com> (raw)
In-Reply-To: <4DDCA0D2.2070604@viscovery.net>
On Wed, May 25, 2011 at 08:25, Johannes Sixt <j.sixt@viscovery.net> wrote:
> Am 5/24/2011 23:45, schrieb Junio C Hamano:
>> * ab/i18n-scripts (2011-05-21) 48 commits
>> (merged to 'next' on 2011-05-23 at 69164a3)
>> ...
>>
>> Rerolled.
>
> I see you promoted ab/i18n-scripts-basic to master. What are your plans
> with this topic? In its current form, git-submodule breaks in an obvious
> way on Windows, and other pitfalls may hide elsewhere.
Aren't you confusing ab/i18n-scripts-basic with ab/i18n-scripts? The
former just adds the infrastructure, the latter adds some eval_gettext
invocations that break on Windows while I haven't submitted some fixup
patches for what's now in *next*, not master.
If anything's breaking on Windows in master it would be the
t/t0201-gettext-fallbacks.sh test which uses some eval_gettext()
calls, but nothing else uses it currently.
> I don't have enough energy to help out with this issue, particularly
> because i18n is not exactly my own itch. Personally, I wouldn't mind the
> fate of the topic if there were a NO_GETTEXT switch that simply avoids all
> the problems on Windows. Is there such a switch?
There isn't and can't be without major re-organizations because
shellscripts don't have something like the C preprocessor.
But I'll just fix the Windows issue soon and submit a new series for
inclusion in next.
next prev parent reply other threads:[~2011-05-25 9:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 21:45 What's cooking in git.git (May 2011, #11; Tue, 24) Junio C Hamano
2011-05-25 6:25 ` Johannes Sixt
2011-05-25 9:36 ` Ævar Arnfjörð Bjarmason [this message]
2011-05-25 10:29 ` Johannes Sixt
2011-05-25 11:46 ` Ævar Arnfjörð Bjarmason
2011-05-25 15:04 ` Junio C Hamano
2011-05-26 3:28 ` David Aguilar
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='BANLkTi=5koa_f_xqaGvKPrEnKMh7ziOT0g@mail.gmail.com' \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
/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).