From: Alex Shi <seakeel@gmail.com>
To: Ben Guo <ben.guo@openatom.club>, Alex Shi <alexs@kernel.org>,
Yanteng Si <si.yanteng@linux.dev>,
Dongliang Mu <dzm91@hust.edu.cn>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
hust-os-kernel-patches@googlegroups.com
Subject: Re: [PATCH] docs/zh_CN: add --no-merges to git log example in how-to.rst
Date: Sun, 19 Apr 2026 21:32:06 +0800 [thread overview]
Message-ID: <74d5a331-9b44-43ae-90a6-8099b65f4845@gmail.com> (raw)
In-Reply-To: <20260416042647.3646595-1-ben.guo@openatom.club>
Applied thanks!
On 2026/4/16 12:26, Ben Guo wrote:
> Add --no-merges flag to prevent referencing merge commits in the
> through-commit field of translation commit messages.
>
> Signed-off-by: Ben Guo<ben.guo@openatom.club>
> ---
> Documentation/translations/zh_CN/how-to.rst | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/translations/zh_CN/how-to.rst b/Documentation/translations/zh_CN/how-to.rst
> index 7ae5d876588..39ed7054fa3 100644
> --- a/Documentation/translations/zh_CN/how-to.rst
> +++ b/Documentation/translations/zh_CN/how-to.rst
> @@ -257,7 +257,9 @@ Git 和邮箱配置
>
> Update the translation through commit b080e52110ea
> ("docs: update self-protection __ro_after_init status")
> - # 请执行 git log --oneline <您翻译的英文文档路径>,并替换上述内容
> + # 请执行 git log --no-merges --oneline <您翻译的英文文档路径>
> + # 并替换上述内容。注意:应引用实际修改文件内容的 commit,
> + # 而非 merge commit
>
> Signed-off-by: Yanteng Si<si.yanteng@linux.dev>
> # 如果您前面的步骤正确执行,该行会自动显示,否则请检查 gitconfig 文件
> -- 2.53.0
prev parent reply other threads:[~2026-04-19 13:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 4:26 [PATCH] docs/zh_CN: add --no-merges to git log example in how-to.rst Ben Guo
2026-04-16 4:51 ` Dongliang Mu
2026-04-19 13:32 ` Alex Shi [this message]
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=74d5a331-9b44-43ae-90a6-8099b65f4845@gmail.com \
--to=seakeel@gmail.com \
--cc=alexs@kernel.org \
--cc=ben.guo@openatom.club \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=hust-os-kernel-patches@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=si.yanteng@linux.dev \
/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