linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Alex Shi <alex.shi@linux.alibaba.com>
Cc: Bailu Lin <bailu.lin@vivo.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>, Harry Wei <harryxiyou@gmail.com>,
	linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel@vivo.com
Subject: Re: [PATCH] Documentation: Chinese translation of Documentation/arm64/perf.rst
Date: Sat, 26 Sep 2020 14:15:47 -0600	[thread overview]
Message-ID: <20200926141547.0ef26bdb@lwn.net> (raw)
In-Reply-To: <747aff97-8b24-5ac2-e46a-fe34b398deb6@linux.alibaba.com>

On Sat, 26 Sep 2020 22:35:51 +0800
Alex Shi <alex.shi@linux.alibaba.com> wrote:

> Why your patch repeatly has encoding issue which fails on 'git am'
> Could you like to check the problem before send out?
> Could you please fix your editor issue by Documentation/process/email-clients.rst
> or send patch by git send-email.
> 
> And please don't waste other time on meaningless issue again!

The way to be sure you have solved this kind of problem is to first email
the patch to you, then be sure that what you receive can be applied.
Please get to the point where that works, then I'll be glad to apply your
translations.

Thanks,

jon

  reply	other threads:[~2020-09-26 20:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-26 10:22 [PATCH] Documentation: Chinese translation of Documentation/arm64/perf.rst Bailu Lin
2020-09-26 14:35 ` Alex Shi
2020-09-26 20:15   ` Jonathan Corbet [this message]
2020-09-27  2:12     ` Alex Shi
2020-09-28  6:59       ` 林白鹭
2020-10-28 13:48 Bailu Lin
2020-10-29  5:55 ` Alex Shi
2020-10-29 15:14 Bailu Lin
2020-10-30  2:33 ` Alex Shi

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=20200926141547.0ef26bdb@lwn.net \
    --to=corbet@lwn.net \
    --cc=alex.shi@linux.alibaba.com \
    --cc=bailu.lin@vivo.com \
    --cc=catalin.marinas@arm.com \
    --cc=harryxiyou@gmail.com \
    --cc=kernel@vivo.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=will@kernel.org \
    /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).