From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Christian Brauner <brauner@kernel.org>
Cc: "Kernel.org Tools" <tools@kernel.org>,
Christian Brauner <christian@amutable.com>
Subject: Re: [PATCH b4] send: add --in-reply-to option for threading cover letters
Date: Fri, 6 Mar 2026 12:26:57 -0500 [thread overview]
Message-ID: <20260306-rare-spotted-wasp-adc84c@lemur> (raw)
In-Reply-To: <20260306-biobauer-mondfinsternis-cc602b2b9c3e@brauner>
On Fri, Mar 06, 2026 at 05:17:57PM +0100, Christian Brauner wrote:
> > I don't see a way to reconcile what you're trying to do and keeping automation
> > working reliably, do you?
>
> Yeah, I wasn't aware that this is a limitation. If this isn't super
> uncommon, than it is broken with similar mail chains. Good to know that
> this breaks b4.
>
> Maybe what Vlastimil proposed would serve at least a similar purpose
> where it adds the people on the bug report to the Cc and automatically
> inserts a Link: to the report in the message or the commit.
Right, so if I understand it correctly, we want to be able to post a "here's a
related patch" but without it being confused as a patch within the same
series. I think one way to accomplish this would be to post the patch under
the scissors, like so:
Hey, how about this patch...
-- >8 --
From: ...
Subject: [PATCH ...] Unrelated Foo Patch
This is foo patch for bar.
git --diff ...
I *think* this would do the right thing, but I need to test it first. From
your perspective, would this do what you're looking for?
Regards,
--
KR
next prev parent reply other threads:[~2026-03-06 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 14:13 [PATCH b4] send: add --in-reply-to option for threading cover letters Christian Brauner
2026-03-06 14:36 ` Vlastimil Babka (SUSE)
2026-03-06 15:02 ` Konstantin Ryabitsev
2026-03-06 15:26 ` Christian Brauner
2026-03-06 15:41 ` Konstantin Ryabitsev
2026-03-06 16:17 ` Christian Brauner
2026-03-06 17:26 ` Konstantin Ryabitsev [this message]
2026-03-07 14:11 ` Christian Brauner
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=20260306-rare-spotted-wasp-adc84c@lemur \
--to=konstantin@linuxfoundation.org \
--cc=brauner@kernel.org \
--cc=christian@amutable.com \
--cc=tools@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