From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Andreas Ericsson <ae@op5.se>
Cc: "Dimitris Glezos" <glezos@indifex.com>,
"Ævar Arnfjörð" <avarab@gmail.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: Tue, 14 Jun 2011 15:42:12 +0530 [thread overview]
Message-ID: <BANLkTinkc6yZ39JVtBaENikFj5xPKnh9mw@mail.gmail.com> (raw)
In-Reply-To: <4DF726F4.3000204@op5.se>
Hi Andreas,
Andreas Ericsson writes:
> It's always better to start coding on changes and then show how those
> changes make life easier for people than to suggest something out of
> thin air and start a discussion about it before applying any work.
Yes, this would normally be the case. My apologies for being unclear
about the purpose of the original email: It's not a sales pitch where
I'm trying to sell one translation system - I'm merely trying to find
out what features the community at large would like from an abstract
web-based translation engine; what should it look like so that it fits
into our current patch/ review system? What this translates to in
terms of work: evaluation various translation systems, and writing the
necessary features into the one that comes closest to what we want.
At a glance, Transifex seems to be a good option, but I could easily
be wrong about that.
-- Ram
next prev parent reply other threads:[~2011-06-14 10:12 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 [this message]
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
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=BANLkTinkc6yZ39JVtBaENikFj5xPKnh9mw@mail.gmail.com \
--to=artagnon@gmail.com \
--cc=ae@op5.se \
--cc=avarab@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).