git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [L10N] please review a batch l10n update for Git 2.2.0 final

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 20, 2014, 23:00 UTC
Message-ID
<xmqqmw7l1nq5.fsf@gitster.dls.corp.google.com>
In-Reply-To
<CANYiYbH5-eDSkq8LQsyixMsDh6e9ZA7nTVib_GbdK5BQ6vE6OA@mail.gmail.com>
Jiang Xin <worldhello.net@gmail.com> writes:
Show 21 quoted lines
> 2014-11-20 16:04 GMT+08:00 Jiang Xin <worldhello.net@gmail.com>:
>> 2014-11-20 14:31 GMT+08:00 Ralf Thielow <ralf.thielow@gmail.com>:
>>>>
>>>> NOTE for Ralf:  After I updated de.po, there are 3 fuzzies instead of one.
>>>> I can only fix one of them.
>>>>
>>>
>>> I just send a pull-request to you. It seems I have forgotten one git.pot update.
>>
>> Merged.  I also see a nice workaround in your commit.  It's a fix for the issue
>> you reported [1] yesterday on our side. ;-)
>>
>>      msgid "check"
>>     +msgstr "check|on-demand"
>>
>> [1]: http://www.spinics.net/lists/git/msg241964.html
>
> Another batch update:
>
> commit 7ba2ba7d12163a8f9a9947d7880bd26f2970d4c5
> ...

I've pushed out what should be -rc3 minus l10n changes and try to make sure there will be no N_() and _() changes.

Let's do a 2.2-rc3 as the last round of this cycle tomorrow. I've fetched up to your 7ba2ba7 but haven't merged it yet, just in case you will have further updates. Otherwise, 2.2-rc3 will be what is at the tip of 'master' today with 7ba2ba7 merged in.

Thanks.
Previous: Jiang XinNext: Jiang Xin
Message 5 of 8 in “[L10N] please review a batch l10n update for Git 2.2.0 final”
  1. Jiang XinNov 20, 2014
  2. Ralf ThielowNov 20, 2014
  3. Jiang XinNov 20, 2014
  4. Jiang XinNov 20, 2014
  5. Junio C HamanoNov 20, 2014
  6. Jiang XinNov 21, 2014
  7. Junio C HamanoNov 21, 2014
  8. Peter KreftingNov 20, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.