Jeff King venit, vidit, dixit 13.09.2012 20:00:
On Thu, Sep 13, 2012 at 10:30:52AM -0700, Junio C Hamano wrote:
But it should not be per-command, but per-message, and
should include all output that is not diagnostic and is not
machine-parseable (e.g., what I mentioned above,
On Fri, Sep 14, 2012 at 5:41 PM, Michael J Gruber
g...@drmicha.warpmail.net wrote:
For those proficient in 2 languages it's desirable to switch per project
because it's likely they participate in projects with different $LANG
preferences. Again, that means localizing everything(*).
On Wed, Sep 12, 2012 at 11:18:06AM -0700, Junio C Hamano wrote:
I am so far taking the silence in the thread to mean they do not mind
seeing the diffstat summary untranslated and they do not mind seeing
it in Klingon, as long as the three numbers are there with (+) and (-)
markings.
On Thu, Sep 13, 2012 at 10:52:08AM -0700, Junio C Hamano wrote:
Junio C Hamano gits...@pobox.com writes:
But it should not be per-command, but per-message, and
should include all output that is not diagnostic and is not
machine-parseable (e.g., what I mentioned above,
Should I interpret the silence as I don't care, if you want it, go
for it or not acceptable, but no reasons given? I'd like some form
of it in. Reverting the i18n diffstat patch is the last resort that I
really don't want to do.
On Sun, Aug 26, 2012 at 2:26 AM, Nguyễn Thái Ngọc Duy
Nguyen Thai Ngoc Duy pclo...@gmail.com writes:
Should I interpret the silence as I don't care, if you want it, go
for it or not acceptable, but no reasons given?
I do not speak for the others, but the reason I didn't respond is
none of the above. It is somewhere between Meh and Anything that
The l10n effort leads to a situation where a contributor can submit a
patch with some auto-generated information in his language, which may
not be the team's language. We need to make sure exchange medium like
patch is always in a common language that the team understands.
Now this team language
7 matches
Mail list logo
