From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Roy Kollen Svendsen <roykollensvendsen@gmail.com>,
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:45:57 +0200 [thread overview]
Message-ID: <ZtIFVfVvWnm67wnX@landeda> (raw)
In-Reply-To: <20240830190012.4ba5a5dc@windsurf>
Thomas, All,
On 2024-08-30 19:00 +0200, Thomas Petazzoni spake thusly:
> 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.
[--SNIP--]
> 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?
I too am not fond of threaded iterations, and I prefer a new thread be
opened for each iteration.
If submitters are going as far as to use --in-reply-to, then can as well
reference the original thread in the post-commit changelog, or in a
cover-letter.
I also like to have such a reference, as I can go and skim over the
previous reviews to assess the changes. So, an automatically-superseded
patch(set) in patchwork is rather detrimental to my workflow, in fact.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-08-30 17:46 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
2024-08-30 17:45 ` Yann E. MORIN [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=ZtIFVfVvWnm67wnX@landeda \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=romain.naour@smile.fr \
--cc=roykollensvendsen@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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.