All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Shi <alex.shi@linux.alibaba.com>
To: Jonathan Corbet <corbet@lwn.net>, Yanteng Si <siyanteng@loongson.cn>
Cc: Harry Wei <harryxiyou@gmail.com>,
	Yanteng Si <siyanteng01@gmail.com>,
	linux-doc@vger.kernel.org, Huacai Chen <chenhuacai@gmail.com>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: Re: [PATCH 1/4] doc/zh_CN: add mips index.rst translation
Date: Tue, 12 Jan 2021 10:06:32 +0800	[thread overview]
Message-ID: <6f4c0e94-7a1f-d30d-51d3-5adb9d6498de@linux.alibaba.com> (raw)
In-Reply-To: <20210111125724.689a7765@lwn.net>



在 2021/1/12 上午3:57, Jonathan Corbet 写道:
> On Mon, 11 Jan 2021 19:33:58 +0800
> Yanteng Si <siyanteng@loongson.cn> wrote:
> 
>> This patch translates Documentation/mips/index.rst into Chinese.
>>
>> Signed-off-by: Yanteng Si <siyanteng@loongson.cn>
>> ---
>>  .../translations/zh_CN/mips/index.rst         | 29 +++++++++++++++++++
>>  1 file changed, 29 insertions(+)
>>  create mode 100644 Documentation/translations/zh_CN/mips/index.rst
> 
> So I am confused by all of this; I've received a few variants of this
> patch set; this one is not threaded properly. It looks like Alex reviewed
> some of the previous versions, but you don't have his Reviewed-by tags
> here.
> 

Hi Yanteng,

You could resend the 1-4 patches as a new thread v6 version, all with my 
Reviewed-by.

Thanks
Alex

> I will drop these; could you please straighten this all up and send me a
> version of the series that is ready to be merged?
> 
> Thanks,
> 
> jon
> 

  reply	other threads:[~2021-01-12  2:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 11:33 [PATCH 1/4] doc/zh_CN: add mips index.rst translation Yanteng Si
2021-01-11 19:57 ` Jonathan Corbet
2021-01-12  2:06   ` Alex Shi [this message]
2021-01-12  4:16   ` teng sterling

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=6f4c0e94-7a1f-d30d-51d3-5adb9d6498de@linux.alibaba.com \
    --to=alex.shi@linux.alibaba.com \
    --cc=chenhuacai@gmail.com \
    --cc=corbet@lwn.net \
    --cc=harryxiyou@gmail.com \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=siyanteng01@gmail.com \
    --cc=siyanteng@loongson.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.