From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Dimitris Glezos <glezos@indifex.com>,
Git List <git@vger.kernel.org>,
Jonathan Nieder <jrnieder@gmail.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: Using Transifex in git.git
Date: Wed, 15 Jun 2011 22:58:09 +0200 [thread overview]
Message-ID: <BANLkTimSKGdRKCOzVWZ3gmX_xBUwHoDuaw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikLJJwfGJp_nshRXGSb-yGOshwzTg@mail.gmail.com>
On Tue, Jun 14, 2011 at 11:37, Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:
To clarify a bit. I think it'd be great if we can get more
translations through any scheme possible.
However, I'd personally prefer if this was delayed a bit until the
outstanding po/*.po patches I have have landed in master. I already
have those locally ready for submission, I'm just going to submit them
after my current series hits master.
The timeline on that is entirely dependent on when Junio merges my
patches down.
But that's just my 0.02c. I don't think I own i18n in any way, so if
someone wants to set up some web ui, gather PO files, and submit them
that's great. More power to them.
> * Any way of editing the translations will have to comply with git's
> normal patch submission process.
Also, I just mentioned this because those are our existing patch
submission guidelines, which I thought would be reasonable to assume
would be the same in this case. Whether we observe this I think would
be something for the maintainer to answer.
Personally I think signed-off-by is silly, and wouldn't mind if we got
new translations in one giant commit with a crappy commit message, but
I didn't make the rules.
next prev parent reply other threads:[~2011-06-15 20:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 5:57 Using Transifex in git.git Ramkumar Ramachandra
2011-06-14 9:16 ` Andreas Ericsson
2011-06-14 10:12 ` Ramkumar Ramachandra
2011-06-14 9:37 ` Ævar Arnfjörð Bjarmason
2011-06-14 11:02 ` Ramkumar Ramachandra
2011-06-14 12:07 ` Andreas Ericsson
2011-06-15 7:33 ` Ramkumar Ramachandra
2011-06-15 8:22 ` Andreas Ericsson
2011-06-15 10:10 ` Ramkumar Ramachandra
2011-06-15 20:40 ` Ævar Arnfjörð Bjarmason
2011-06-15 20:58 ` Ævar Arnfjörð Bjarmason [this message]
2011-06-15 13:21 ` Erik Faye-Lund
2011-06-15 13:45 ` Michael Witten
2011-06-15 20:43 ` Æ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=BANLkTimSKGdRKCOzVWZ3gmX_xBUwHoDuaw@mail.gmail.com \
--to=avarab@gmail.com \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=glezos@indifex.com \
--cc=jrnieder@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.
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).