The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Yanteng Si <si.yanteng@linux.dev>
To: Dongliang Mu <dzm91@hust.edu.cn>, Alex Shi <alexs@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Geert Uytterhoeven <geert+renesas@glider.be>
Cc: hust-os-kernel-patches@googlegroups.com,
	Hu Haowen <2023002089@link.tyut.edu.cn>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] docs/zh_CN: update the translation of process/submitting-patches.rst
Date: Fri, 18 Oct 2024 15:32:15 +0800	[thread overview]
Message-ID: <dbabf6eb-a1bf-401f-9159-605bc74e182c@linux.dev> (raw)
In-Reply-To: <aac937f3-f147-49b8-8408-9f8f4d00735e@linux.dev>




在 2024/10/18 15:12, Yanteng Si 写道:
>
>
>
> 在 2024/10/18 09:54, Dongliang Mu 写道:
>> Update to commit eb5ed2fae197 ("docs: submitting-patches: Advertise b4")
>>
>> scripts/checktransupdate.py reports:
>>
>> Documentation/translations/zh_CN/process/submitting-patches.rst
>> commit eb5ed2fae197 ("docs: submitting-patches: Advertise b4")
>> commit 413e775efaec ("Documentation: fix links to mailing list 
>> services")
>> 2 commits needs resolving in total
>>
>> Signed-off-by: Dongliang Mu <dzm91@hust.edu.cn>
> Reviewed-by: Yanteng Si <si.yanteng@linux.dev>
>
I apologize, I signed off repeatedly (in v1).

Dongliang, Similar patches can be grouped into a single patch set,
which would make the review process easier.

run:
git format-patch -n <the number of patches> -v <version>  --cover-letter 
--thread=shallow

Thanks,
Yanteng

  reply	other threads:[~2024-10-18  7:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18  1:54 [PATCH v2] docs/zh_CN: update the translation of process/submitting-patches.rst Dongliang Mu
2024-10-18  7:12 ` Yanteng Si
2024-10-18  7:32   ` Yanteng Si [this message]
2024-10-18  8:46     ` Dongliang Mu
2024-10-21 15:36 ` Jonathan Corbet

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=dbabf6eb-a1bf-401f-9159-605bc74e182c@linux.dev \
    --to=si.yanteng@linux.dev \
    --cc=2023002089@link.tyut.edu.cn \
    --cc=alexs@kernel.org \
    --cc=corbet@lwn.net \
    --cc=dzm91@hust.edu.cn \
    --cc=geert+renesas@glider.be \
    --cc=hust-os-kernel-patches@googlegroups.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.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