git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org, Erik Faye-Lund <kusmabite@gmail.com>
Subject: Re: Stable ab/i18n branch
Date: Thu, 14 Oct 2010 20:44:13 +0000	[thread overview]
Message-ID: <AANLkTim-2V_XtWVLFbWS_A-0rFNmuDvtR58aanxKL-O2@mail.gmail.com> (raw)
In-Reply-To: <20101014200027.GA18813@burratino>

On Thu, Oct 14, 2010 at 20:00, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Ævar Arnfjörð Bjarmason wrote:
>
>> Could you please pick up the 160 commit version of this at:
>>
>>     git://github.com/avar/git.git ab/i18n
>
> This is a "give an inch and they'll ask for a mile" sort of thing, but
> would it be possible to maintain a stable branch with the i18n
> infrastructure that only gets rebased when there is reorganization
> going on?
>
> The gettextization and translations are rebased for other reasons (to
> avoid going crazy), I know.  But with the infrastructure it is starting
> to be hard to track what changes over time.

I could do that, but I've been hoping that it just gets picked up for
the `next -> master` process of git.git itself and *that* becomes the
stable target.

But I have no idea what's going on at the other end, i.e. there's no
comments about it in the "What's cooking in git.git" posts or
elsewhere. So it's hard to know whether something like this is needed.

It's been about as ready as it's ever going to get for about a month
now. The libcharset.h change that was added to it a week or so ago
could have come on top of the series. But since it hadn't been merged
anywhere I rebased and inserted that earlier in the series for the
relatively obscure case of helping bisectability on Windows.

I'm starting to get the feeling that there isn't much interest in i18n
support at all. It didn't show up highly in the wanted features in the
Git survey, and most of the translations have been contributed by
people I've poked directly.

So maybe I should just get the hint and drop it *shrug*. I don't have
much time to spend on this these days since I've been moving /
starting a new job. So if it's not going to get merged into core I
might as well do something else.

(I'm not being bitter, really. Just practical)

  reply	other threads:[~2010-10-14 20:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-14  4:46 What's cooking in git.git (Oct 2010, #01; Wed, 13) Junio C Hamano
2010-10-14  5:51 ` Nazri Ramliy
2010-10-14  9:23 ` Ævar Arnfjörð Bjarmason
2010-10-14 20:00   ` Stable ab/i18n branch Jonathan Nieder
2010-10-14 20:44     ` Ævar Arnfjörð Bjarmason [this message]
2010-10-14 20:54       ` Jonathan Nieder
2010-10-14 21:18         ` Ævar Arnfjörð Bjarmason
2010-10-14 21:26           ` Sverre Rabbelier
2010-10-14 21:50           ` Jon Seymour
2010-10-15  4:54             ` Ævar Arnfjörð Bjarmason
2010-10-15  0:07           ` Jonathan Nieder
2010-10-15  5:16             ` Ævar Arnfjörð Bjarmason
2010-10-15  5:28               ` Jonathan Nieder
2010-10-15  5:35                 ` Ævar Arnfjörð Bjarmason
2010-10-17  4:44     ` Junio C Hamano
2010-10-17 12:33       ` Ævar Arnfjörð Bjarmason
2010-10-17 15:59         ` Jonathan Nieder
2010-10-18 23:39         ` Junio C Hamano
2010-10-19  6:05           ` Michael J Gruber
2010-10-17  4:43   ` What's cooking in git.git (Oct 2010, #01; Wed, 13) Junio C Hamano
2010-10-21  2:14 ` Johan Herland

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=AANLkTim-2V_XtWVLFbWS_A-0rFNmuDvtR58aanxKL-O2@mail.gmail.com \
    --to=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.com \
    --cc=kusmabite@gmail.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).