public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Yanteng Si <siyanteng@loongson.cn>
Cc: Yanteng Si <siyanteng@loongson.cn>,
	alexs@kernel.org, chenhuacai@kernel.org, jiaxun.yang@flygoat.com,
	linux-doc@vger.kernel.org, realpuyuwang@gmail.com,
	bobwxc@email.cn, siyanteng01@gmail.com
Subject: Re: [PATCH v7 00/11] docs/zh_CN: add core api and openrisc translation
Date: Tue, 20 Apr 2021 16:10:53 -0600	[thread overview]
Message-ID: <87lf9cip3m.fsf@meer.lwn.net> (raw)
In-Reply-To: <cover.1618568135.git.siyanteng@loongson.cn>

Yanteng Si <siyanteng@loongson.cn> writes:

> This series of patches translates core-api/irq/* and openrisc/* into Chinese.
>
> v1 -> v2:
>
> Modify some words under Xiangcheng Wu's suggestion. Thanks for his rewiew!
>
> v2 -> v3:
>
> keep the signs number equal to the title char under Alex's suggestion.
> Thanks for his rewiew!
>
> v3 -> v4:
>
> Add Xiangcheng Wu's review sign to 0002、0003 and 0008; Thanks for his rewiew!
>
> v4 -> v5:
>
> Split 1-7 into a separate series.
>
> v5 -> v6:
>
> Modify the Subject of patches 07 and 11.
> Patch 11 will not be sent if not modified. (name repeat)
>
> Revert to one series because there is no need to split into two series.
>
> v6 -> v7:
>
> Send patch 11 to the series. Thank you Xiangcheng for your help!
>
> Yanteng Si (11):
>   docs/zh_CN: add core-api irq concepts.rst translation
>   docs/zh_CN: add core-api irq irq-affinity.rst translation
>   docs/zh_CN: add core-api irq irq-domain.rst translation
>   docs/zh_CN: add core-api irq irqflags-tracing.rst translation
>   docs/zh_CN: add core-api irq index.rst translation
>   docs/zh_CN: add core-api index.rst translation
>   docs/zh_CN: add core api translation to zh_CN index
>   docs/zh_CN: add openrisc openrisc_port.rst translation
>   docs/zh_CN: add openrisc todo.rst translation
>   docs/zh_CN: add openrisc index.rst translation
>   docs/zh_CN: add openrisc translation to zh_CN index

I have applied this series, thanks.

I have a request for the future, though: when you add a new file, do the
associated index.rst changes *in the same patch*.  Among other things,
that helps bisectability - we'll know which patch adds a build error,
for example.  It's not hugely important for docs, but is a good way to
approach kernel work in general - don't stack up lots of work that only
becomes active as the result of a small patch at the end.

THanks,

jon

  parent reply	other threads:[~2021-04-20 22:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 10:32 [PATCH v7 00/11] docs/zh_CN: add core api and openrisc translation Yanteng Si
2021-04-16 10:32 ` [PATCH v7 01/11] docs/zh_CN: add core-api irq concepts.rst translation Yanteng Si
2021-04-16 10:32 ` [PATCH v7 02/11] docs/zh_CN: add core-api irq irq-affinity.rst translation Yanteng Si
2021-04-16 10:32 ` [PATCH v7 03/11] docs/zh_CN: add core-api irq irq-domain.rst translation Yanteng Si
2021-04-16 10:32 ` [PATCH v7 04/11] docs/zh_CN: add core-api irq irqflags-tracing.rst translation Yanteng Si
2021-04-16 10:32 ` [PATCH v7 05/11] docs/zh_CN: add core-api irq index.rst translation Yanteng Si
2021-04-16 10:32 ` [PATCH v7 06/11] docs/zh_CN: add core-api " Yanteng Si
2021-04-16 10:32 ` [PATCH v7 07/11] docs/zh_CN: add core api translation to zh_CN index Yanteng Si
2021-04-16 10:32 ` [PATCH v7 08/11] docs/zh_CN: add openrisc openrisc_port.rst translation Yanteng Si
2021-04-16 10:32 ` [PATCH v7 09/11] docs/zh_CN: add openrisc todo.rst translation Yanteng Si
2021-04-16 10:32 ` [PATCH v7 10/11] docs/zh_CN: add openrisc index.rst translation Yanteng Si
2021-04-16 10:32 ` [PATCH v7 11/11] docs/zh_CN: add openrisc translation to zh_CN index Yanteng Si
2021-04-16 11:58   ` Wu X.C.
2021-04-20 22:10 ` Jonathan Corbet [this message]
2021-04-21  1:34   ` [PATCH v7 00/11] docs/zh_CN: add core api and openrisc translation 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=87lf9cip3m.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=alexs@kernel.org \
    --cc=bobwxc@email.cn \
    --cc=chenhuacai@kernel.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=realpuyuwang@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox