Re: Please pull git-po master branch

From: Junio C Hamano <gitster@pobox.com>
Date: May 2, 2012, 16:40 UTC
Message-ID: <7vtxzyilid.fsf@alter.siamese.dyndns.org>
In-Reply-To: <87d36n2f2r.fsf@thomas.inf.ethz.ch>

Thomas Rast <trast@student.ethz.ch> writes:

Show 26 quoted lines

> Hi Xin (is that how you are properly addressed?)
> Hi Ralf
>
> Jiang Xin <worldhello.net@gmail.com> writes:
>> Ralf Thielow (3):
>>       l10n: Add the German translation team and initialize de.po
>>       l10n: Initial German translation
>>       l10n: Update German translation
>
> Junio C Hamano <gitster@pobox.com> writes:
>> Both branches pulled; I found it somewhat iffy to *add* new language support
>> on the maintenance track, but decided to let it pass this time.
>> 
>> A new lang.po file is very unlikely to introduce regression to anybody
>> else, so it probably is OK.
>
> Objection.
>
> Jan "jast" Krüger and me had most of the following "in the works", and
> couldn't get it shaped up before the pull request went out.  Any
> translation mistakes are mine, we drafted it in German.
> ...
> To put it bluntly, we have significant concerns with your translation so
> far.  That's usually not a problem in OSS -- release early and release
> and release often -- but the maint release would require you to get it
> Right(tm) the first time.

While I can understand your frustration and trust you enough to believe the issue you are raising for the *.po contents that were merged are very real, it is too late for this round. What happened has happened already.

Sorry about that.

But I have to be able to trust that such differences are resolved between the i18n coordinator and the l10n teams before a pull request comes to me. That's the only way we can scale the process.

> Of course now that it has been released, we'll also have to file patches
> in the true open source spirit.  Sigh.

There is nothing to "Sigh" about.  Mistakes happen, and we learn from it.

Thanks.