From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Roy Kollen Svendsen <roykollensvendsen@gmail.com>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>,
Romain Naour <romain.naour@smile.fr>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] docs/manual: fix description of how to reply to <message-id>
Date: Fri, 30 Aug 2024 19:00:12 +0200 [thread overview]
Message-ID: <20240830190012.4ba5a5dc@windsurf> (raw)
In-Reply-To: <20240830135546.906135-1-roykollensvendsen@gmail.com>
Hello,
+BR maintainers in Cc.
On Fri, 30 Aug 2024 15:55:45 +0200
Roy Kollen Svendsen <roykollensvendsen@gmail.com> wrote:
> Patch v1 not set to 'superseded' when replying to <message-id> with v2.
>
> I'm using git version 2.46.0. The manual says the following is the
> correct way to use the '--in-reply-to' option:
>
> git send-email --in-reply-to=<message-id>
>
> Signed-off-by: Roy Kollen Svendsen <roykollensvendsen@gmail.com>
> ---
> docs/manual/contribute.adoc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
I have applied to master, because it fixes a bug in the doc. But on my
side, I am not a big fan of subsequent iterations being sent as a reply
to the previous iteration. I know it has the advantage that patchwork
marks the previous iteration as Superseded, but I find it a bit
annoying on the mailing list.
What do other BR maintainers think?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-08-30 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 13:55 [Buildroot] [PATCH 1/1] docs/manual: fix description of how to reply to <message-id> Roy Kollen Svendsen
2024-08-30 17:00 ` Thomas Petazzoni via buildroot [this message]
2024-08-30 17:45 ` Yann E. MORIN
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=20240830190012.4ba5a5dc@windsurf \
--to=buildroot@buildroot.org \
--cc=romain.naour@smile.fr \
--cc=roykollensvendsen@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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.