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, #11; Tue, 24)
Date: Wed, 25 May 2011 12:29:12 +0200 [thread overview]
Message-ID: <4DDCD9F8.9080105@viscovery.net> (raw)
In-Reply-To: <BANLkTi=5koa_f_xqaGvKPrEnKMh7ziOT0g@mail.gmail.com>
Am 5/25/2011 11:36, schrieb Ævar Arnfjörð Bjarmason:
> Aren't you confusing ab/i18n-scripts-basic with ab/i18n-scripts?
No, I'm aware of the difference and purposes of the two topics.
>> ... 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.
Well, we do preprocess the shell scripts. Wouldn't it be a matter of
if test -z '@@NO_GETTEXT@@'
then
... regular eval_gettext definition ...
else
... dummy eval_gettext definition ...
fi
with a corresponding extension of the sed script in the Makefile?
> But I'll just fix the Windows issue soon and submit a new series for
> inclusion in next.
Thanks! I just wanted to be sure that ab/i18n-scripts does not end up in
master in a state that leaves Windows in limbo.
-- Hannes
next prev parent reply other threads:[~2011-05-25 10:29 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
2011-05-25 10:29 ` Johannes Sixt [this message]
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=4DDCD9F8.9080105@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).