From: Weijie Yuan <wy@wyuan.org>
To: Dongliang Mu <dzm91@hust.edu.cn>
Cc: Alex Shi <alexs@kernel.org>, Yanteng Si <si.yanteng@linux.dev>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] docs/zh_CN: update maintainer/configure-git.rst
Date: Mon, 16 Nov 2026 22:38:46 +0800 [thread overview]
Message-ID: <avsVdm5rzX_ZxtsP@wyuan.org> (raw)
In-Reply-To: <avsSapW0-wS_gEsz@wyuan.org>
On Mon, Nov 16, 2026 at 10:25:55PM +0800, Weijie Yuan wrote:
> > > Range-diff versus v2:
> >
> > You need to tell your agent to forget about the range-diff.
>
> Sorry, I realized immediately that I forgot to change my template for b4
> cover letter after sending out this. Now deleted.
>
> --- a/.b4-cover-template
> +++ b/.b4-cover-template
> @@ -4,8 +4,6 @@ ${cover}
> ${shortlog}
>
> ${diffstat}
> -
> -${range_diff}
> ---
> base-commit: ${base_commit}
> change-id: ${change_id}
>
> Thanks.
But anyway, for recent series I did not use b4, so absolutely no more
range-diffs will be generated manually. This series was created and
tracked with b4 in August, therefore I continued to use b4 to send out
v3. And yes, I might be better off asking an agent to check it for me.
Will pay more attention, thanks.
prev parent reply other threads:[~2026-11-16 14:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 9:28 [PATCH v3 0/2] docs/zh_CN: update maintainer/configure-git.rst Weijie Yuan
2026-11-09 9:28 ` [PATCH v3 1/2] docs/zh_CN: sync maintainer/configure-git with upstream Weijie Yuan
2026-11-16 14:44 ` Dongliang Mu
2026-11-09 9:28 ` [PATCH v3 2/2] docs/zh_CN: improve maintainer/pull-requests translation Weijie Yuan
2026-11-16 14:44 ` Dongliang Mu
2026-11-16 14:20 ` [PATCH v3 0/2] docs/zh_CN: update maintainer/configure-git.rst Dongliang Mu
2026-11-16 14:25 ` Weijie Yuan
2026-11-16 14:38 ` Weijie Yuan [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=avsVdm5rzX_ZxtsP@wyuan.org \
--to=wy@wyuan.org \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=si.yanteng@linux.dev \
--cc=skhan@linuxfoundation.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 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.