git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jiang Xin <worldhello.net@gmail.com>
Cc: Git List <git@vger.kernel.org>,
	Tran Ngoc Quan <vnwildman@gmail.com>,
	Peter Krefting <peter@softwolves.pp.se>,
	Ralf Thielow <ralf.thielow@googlemail.com>
Subject: Re: Git 1.8.2 l10n round 3
Date: Mon, 25 Feb 2013 09:47:36 -0800	[thread overview]
Message-ID: <7v4nh0z3nr.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CANYiYbHPtW0u80ojHt9xoADVS8S8mVkubb6dUDN_1uwkcTZTww@mail.gmail.com> (Jiang Xin's message of "Mon, 25 Feb 2013 21:24:14 +0800")

Thanks.

  parent reply	other threads:[~2013-02-25 17:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-19  5:50 Git 1.8.2 l10n round 3 Jiang Xin
2013-02-25 13:24 ` Jiang Xin
2013-02-25 17:45   ` Junio C Hamano
2013-02-25 17:47   ` Junio C Hamano [this message]
2013-02-26 10:24     ` Jiang Xin

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=7v4nh0z3nr.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=peter@softwolves.pp.se \
    --cc=ralf.thielow@googlemail.com \
    --cc=vnwildman@gmail.com \
    --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.
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 NNTP newsgroup(s).