From: Junio C Hamano <gitster@pobox•com>
To: Jiang Xin <worldhello.net@gmail•com>
Cc: "Alexander Shopov" <ash@kambanaria•org>,
"Alex Henrie" <alexhenrie24@gmail•com>,
"Ralf Thielow" <ralf.thielow@gmail•com>,
"Jean-Noël Avila" <jn.avila@free•fr>,
"Marco Paolone" <marcopaolone@gmail•com>,
"Changwoo Ryu" <cwryu@debian•org>,
"Vasco Almeida" <vascomalmeida@sapo•pt>,
"Dimitriy Ryazantcev" <DJm00n@mail•ru>,
"Peter Krefting" <peter@softwolves•pp.se>,
"Trần Ngọc Quân" <vnwildman@gmail•com>,
"Git List" <git@vger•kernel.org>
Subject: Re: [GIT PULL] l10n updates for 2.11.0 round 2
Date: Tue, 22 Nov 2016 14:24:15 -0800 [thread overview]
Message-ID: <xmqqwpfvnofk.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CANYiYbFSpUmtv1eO_GE_yRU4CsXzd29qV2LTbXa67d=Uxbw2=Q@mail.gmail.com> (Jiang Xin's message of "Tue, 22 Nov 2016 23:11:31 +0800")
Jiang Xin <worldhello.net@gmail•com> writes:
> Git 2.11.0-rc2 introduced a very small l10n update. Because the
> update windows will be
> closed tomorrow, I made a batch updates. See commit:
>
> * https://github.com/git-l10n/git-po/commit/275588f93
>
> I have a reduced diff for this commit using a custom diff driver, see:
>
> * https://gist.github.com/jiangxin/6384b1e865249228e00385fab84ef3f3
>
>
> 2016-11-22 22:59 GMT+08:00 Jiang Xin <worldhello.net@gmail•com>:
>> Hi Junio,
>>
>> The following changes since commit 1310affe024fba407bff55dbe65cd6d670c8a32d:
>>
>> Git 2.11-rc2 (2016-11-17 13:47:36 -0800)
>>
>> are available in the git repository at:
>>
>> git://github.com/git-l10n/git-po tags/l10n-2.11.0-rnd2
Thanks, pulled.
FYI, we seem to need a bit more time on the code front so we'll have
an unscheduled 2.11-rc3 tomorrow. The final one will be near the
end of the month, tenatively scheduled on Nov 29th.
prev parent reply other threads:[~2016-11-22 22:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 14:59 [GIT PULL] l10n updates for 2.11.0 round 2 Jiang Xin
2016-11-22 15:11 ` Jiang Xin
2016-11-22 22:24 ` Junio C Hamano [this message]
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=xmqqwpfvnofk.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=DJm00n@mail$(echo .)ru \
--cc=alexhenrie24@gmail$(echo .)com \
--cc=ash@kambanaria$(echo .)org \
--cc=cwryu@debian$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=jn.avila@free$(echo .)fr \
--cc=marcopaolone@gmail$(echo .)com \
--cc=peter@softwolves$(echo .)pp.se \
--cc=ralf.thielow@gmail$(echo .)com \
--cc=vascomalmeida@sapo$(echo .)pt \
--cc=vnwildman@gmail$(echo .)com \
--cc=worldhello.net@gmail$(echo .)com \
/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