From: Junio C Hamano <gitster@pobox.com>
To: Jiang Xin <worldhello.net@gmail.com>
Cc: Dimitriy Ryazantcev <dimitriy.ryazantcev@gmail.com>,
Alex Henrie <alexhenrie24@gmail.com>,
Git List <git@vger.kernel.org>
Subject: Re: [GIT PULL] l10n updates for 2.11.0 round 3 with ru and ca translations
Date: Tue, 29 Nov 2016 11:36:48 -0800 [thread overview]
Message-ID: <xmqqbmwyf57z.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CANYiYbHYaOUwJo_8Vc4vAYatC+Xu09fWLw5q+T7W_7_xwuD7Nw@mail.gmail.com> (Jiang Xin's message of "Tue, 29 Nov 2016 21:30:33 +0800")
Jiang Xin <worldhello.net@gmail.com> writes:
> Final l10n updates for this release cycle, please pull.
Thanks!
prev parent reply other threads:[~2016-11-29 19:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 13:30 [GIT PULL] l10n updates for 2.11.0 round 3 with ru and ca translations Jiang Xin
2016-11-29 19:36 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqbmwyf57z.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=alexhenrie24@gmail.com \
--cc=dimitriy.ryazantcev@gmail.com \
--cc=git@vger.kernel.org \
--cc=worldhello.net@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).