From: Jonathan Corbet <corbet@lwn.net>
To: Wu XiangCheng <bobwxc@email.cn>, Alex Shi <alexs@kernel.org>,
Yanteng Si <siyanteng@loongson.cn>
Cc: linux-doc@vger.kernel.org
Subject: Re: [PATCH 0/2] docs/zh_CN: sync reporting-issues.rst to 247097e2bbff4
Date: Tue, 17 May 2022 13:24:30 -0600 [thread overview]
Message-ID: <877d6kvu6p.fsf@meer.lwn.net> (raw)
In-Reply-To: <cover.1652792205.git.bobwxc@email.cn>
Wu XiangCheng <bobwxc@email.cn> writes:
> sync zh_CN/admin-guide/reporting-issues.rst to newest version
> (commit 247097e2bbff4)
>
> There are two patches in the same name, the first acturally been
> reviewed by Alex and Yanteng last year , see <https://lore.kernel.org/linux-doc/CAMU9jJor_V_G6wG1vWnDvgQADeXaPxg9E47w27nk_sBNGJpuEg@mail.gmail.com/>,
> but not been picked up yet. So I rebase it to newest docs-next and resend
> it. Then bring a new sync commit.
I'm not quite sure what happened with that patch, but I do know that
posting multiple patches with the same subject line is a recipe for
confusion; please don't do that.
In this case, is there any reason to not just merge those two patches
together? Then make the subject line read something like "Update the
translation of reporting-issues.rst to 5.18" or something like that.
Thanks,
jon
next prev parent reply other threads:[~2022-05-17 19:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 13:16 [PATCH 0/2] docs/zh_CN: sync reporting-issues.rst to 247097e2bbff4 Wu XiangCheng
2022-05-17 17:08 ` [PATCH 1/2] docs/zh_CN: sync reporting-issues.rst Wu XiangCheng
2022-05-17 17:09 ` [PATCH 2/2] " Wu XiangCheng
2022-05-17 19:24 ` Jonathan Corbet [this message]
2022-05-18 3:16 ` [PATCH v2] docs/zh_CN: Update translation of reporting-issues.rst to 5.18 Wu XiangCheng
2022-05-18 3:24 ` Alex Shi
2022-06-13 17:33 ` 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=877d6kvu6p.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=alexs@kernel.org \
--cc=bobwxc@email.cn \
--cc=linux-doc@vger.kernel.org \
--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.