From: Rodrigo Rosenfeld Rosas <rr.rosas@gmail•com>
To: Pat Thoyts <patthoyts@users•sourceforge.net>
Cc: Junio C Hamano <gitster@pobox•com>,
Drew Northup <drew.northup@maine•edu>,
git@vger•kernel.org
Subject: Re: Translation inclusion criteria
Date: Thu, 31 Mar 2011 10:16:46 -0300 [thread overview]
Message-ID: <4D947EBE.5030708@gmail.com> (raw)
In-Reply-To: <87tyekpxg5.fsf@fox.patthoyts.tk>
Em 30-03-2011 10:08, Pat Thoyts escreveu:
> Rodrigo Rosenfeld Rosas<rr.rosas@gmail•com> writes:
>
>> Em 29-03-2011 15:59, Junio C Hamano escreveu:
>>> Drew Northup<drew.northup@maine•edu> writes:
>>>
>>>> On Tue, 2011-03-22 at 09:57 -0300, Rodrigo Rosenfeld Rosas wrote:
>>>>> Hi, I've followed the instructions in git-gui/po/README in 2008 but
>>>>> pt.po was never included in master. Now I've just updated it.
>>>>>
>>>>> Is there anything else I should do for it being merged to master? What
>>>>> is the criteria for including new translations?
>>>> ...
>>>> Rodrigo,
>>>> Internationalization of Git is very much an ongoing process. I suspect
>>>> that has something to do with the uptake of your contribution. Ævar may
>>>> have more information.
>>> All the git-gui changes come through Pat Thoyts these days; Ævar has
>>> nothing to with git-gui i18n/l10n (except perhaps as a translator to his
>>> own language, but I don't see his name in the shortlog).
>>>
>>> Perhaps the submission was sent with wrong Cc:; I don't pay attention to
>>> git-gui and gitk l10n patches myself.
>> Sorry, I think I'm missing something. From the mentioned README, it
>> seems we're supposed to push our changes to the mob branch of
>> mob@repo•or.cz:/srv/git/git-gui/git-gui-i18n.git/, which has write
>> access enabled for everyone.
>>
>> That's what I've done. I couldn't find any mention in the README about
>> having to send some mail after that.
>>
>> I'll wait for instructions from Pat Thoyts to understand better what
>> should be my next step...
>>
>> Thanks,
>>
>> Rodrigo.
> It's best to just send a patch to me and this list based against one
> of the current branches (master/maint/pu). The i18n fork was done for
> the original work adding i18n to git-gui and hasn't been kept up to date
> since 2008.
Ok, thanks. I've just noticed pt_br.po was already included some days
ago on March 26 by Junio Hamano and it is up-to-date in the master branch.
But it would be great to update the README to replace those instructions
regarding mob@repo•or.cz by the new instruction for sending the patches
by e-mail.
Best regards,
Rodrigo.
next prev parent reply other threads:[~2011-03-31 13:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 12:57 Translation inclusion criteria Rodrigo Rosenfeld Rosas
2011-03-29 16:59 ` Drew Northup
2011-03-29 18:59 ` Junio C Hamano
2011-03-29 19:24 ` Rodrigo Rosenfeld Rosas
2011-03-30 13:08 ` Pat Thoyts
2011-03-31 13:16 ` Rodrigo Rosenfeld Rosas [this message]
2011-03-31 15:26 ` Pat Thoyts
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=4D947EBE.5030708@gmail.com \
--to=rr.rosas@gmail$(echo .)com \
--cc=drew.northup@maine$(echo .)edu \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=patthoyts@users$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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