public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Andy Deng <theandy.deng@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: [PATCH v2 1/3] zh_CN/CodingStyle: improve translation
Date: Thu, 26 Jan 2017 15:40:22 -0700	[thread overview]
Message-ID: <20170126154022.49cf4151@lwn.net> (raw)
In-Reply-To: <20170125041433.9713-1-theandy.deng@gmail.com>

On Wed, 25 Jan 2017 12:14:31 +0800
Andy Deng <theandy.deng@gmail.com> wrote:

> Some of the sentences in Chapters 19 and 20 are re-translated:
> 
> - Fixed translation errors in Section 2 of Chapter 19 to prevent
>   misleading readers;
> - Retranslate some sentences to make the translation more clear and
>   accurate.

OK, I've applied the whole set, thanks.

One thing, though: your messages came through with this header:

	Content-Type: text/plain; charset=y

The screwy "charset=y" puts "git am" into a severely uncooperative mood,
so I had to edit your messages by hand to apply them.   Mauro (copied), do
I remember correctly that you figured out how that was happening to your
emails? It would be good to get that understood, documented, and maybe
even fixed...

Thanks,

jon

  parent reply	other threads:[~2017-01-26 22:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25  4:14 [PATCH v2 1/3] zh_CN/CodingStyle: improve translation Andy Deng
2017-01-25  4:14 ` [PATCH v2 2/3] zh_CN/CodingStyle: Convert to ReST markup Andy Deng
2017-01-25  4:14 ` [PATCH v2 3/3] docs/zh_CN: Add coding-style into docs build system Andy Deng
2017-01-26 22:40 ` Jonathan Corbet [this message]
2017-01-27  2:28   ` [PATCH v2 1/3] zh_CN/CodingStyle: improve translation Andy Deng

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=20170126154022.49cf4151@lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=theandy.deng@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