From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Roadmap for 1.7.9
Date: Tue, 6 Dec 2011 01:02:16 +0100 [thread overview]
Message-ID: <CACBZZX6=eYaebLdQrLvvaXPKFLYj_-7QGrco7gnXPjh8hjOQ=w@mail.gmail.com> (raw)
In-Reply-To: <7vr50ik55n.fsf@alter.siamese.dyndns.org>
On Mon, Dec 5, 2011 at 23:47, Junio C Hamano <gitster@pobox.com> wrote:
> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>
>> On Mon, Dec 5, 2011 at 21:07, Junio C Hamano <gitster@pobox.com> wrote:
>>
>>> Now, here are the biggies that we would want to try to have in reasonable
>>> shape before the next release.
>>
>> I'd like to get the i18n series into 1.7.9 as well. I think it's ready
>> as-is but some minor issues are sure to arise.
>
> Surely.
>
> My impression was that the part that can have interactions with the
> existing codebase is already in, and it is just the matter of updating
> what _() ans Q_() actually do, which can be reverted out quickly if it
> turns out to be necessary, and that was why I didn't count it as part of
> the "biggies" that make us worry.
That's the gist of it. But it's still a massive 1300 line patch,
which:
* Calls setlocale(LC_MESSAGES)
* Uses an evil trick to only call setlocale(LC_CTYPE) while loading
message catalogs
* Might have some portability problems on more obscure OS's.
* Has some tests I've only tested on Linux, FreeBSD and Solaris
So it might have some little surprises, and it would be nice to have
it in master early on so we'll give it plenty of time to cook and
discover any issues before 1.7.9.
next prev parent reply other threads:[~2011-12-06 0:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 20:07 Roadmap for 1.7.9 Junio C Hamano
2011-12-05 21:24 ` Ævar Arnfjörð Bjarmason
2011-12-05 22:47 ` Junio C Hamano
2011-12-06 0:02 ` Ævar Arnfjörð Bjarmason [this message]
2011-12-06 11:16 ` Nguyen Thai Ngoc Duy
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACBZZX6=eYaebLdQrLvvaXPKFLYj_-7QGrco7gnXPjh8hjOQ=w@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).