From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Cooking of the ab/i18n series
Date: Thu, 5 Aug 2010 21:09:52 +0000 [thread overview]
Message-ID: <AANLkTi=bnDgUsnBCv5493sH9eY5hg0S2YPywKba9jD20@mail.gmail.com> (raw)
On Wed, Aug 4, 2010 at 22:24, Junio C Hamano <gitster@pobox.com> wrote:
Since we're asking about the status of series...
> * tr/ab-i18n-fix (2010-07-25) 1 commit
> - tests: locate i18n lib&data correctly under --valgrind
> (this branch uses ab/i18n.)
> * ab/i18n (2010-07-19) 2 commits
> - tests: rename test to work around GNU gettext bug
> - Add infrastructure for translating Git with gettext
> (this branch is used by tr/ab-i18n-fix.)
Do you have any plans for when to merge the i18n series?
It's been cooking for a while now, and it'll need a lot of follow-up
work (gettextizing) once it gets merged.
I don't have infinite time to do that, so sooner rather than later
would be better if we're going to e.g. have a fully localized Git 1.8.
I haven't been sending these follow up patches due to the reasons I
already cited. They're pretty much guaranteed to conflict with other
things in-flight.
If you're not comfortable with merging it soon for whatever reason
then perhaps I could submit something to add a no-op N_() macro to Git
in the interim. Then we could just do s/N_/_/ on the source tree once
the real series gets merged.
next reply other threads:[~2010-08-05 21:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 21:09 Ævar Arnfjörð Bjarmason [this message]
2010-08-05 22:18 ` Cooking of the ab/i18n series Junio C Hamano
2010-08-06 12:33 ` Ævar Arnfjörð Bjarmason
2010-08-06 13:30 ` Junio C Hamano
2010-08-06 14:03 ` Ævar Arnfjörð Bjarmason
2010-08-06 15:48 ` Junio C Hamano
2010-08-06 17:01 ` Ævar Arnfjörð Bjarmason
2010-08-06 19:28 ` Ævar Arnfjörð Bjarmason
2010-08-06 23:01 ` Junio C Hamano
2010-08-07 1:13 ` Ævar Arnfjörð Bjarmason
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='AANLkTi=bnDgUsnBCv5493sH9eY5hg0S2YPywKba9jD20@mail.gmail.com' \
--to=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).