From: Alex Elder <elder@ieee.org>
To: users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: RFC: Superseded-by: follow-up trailer
Date: Tue, 13 Apr 2021 15:53:50 -0500 [thread overview]
Message-ID: <fd732fc9-83a9-5502-fba5-f08317bdcaf3@ieee.org> (raw)
In-Reply-To: <20210413204932.yovoa7njwc56jo5v@nitro.local>
On 4/13/21 3:49 PM, Konstantin Ryabitsev wrote:
> Hi, all:
>
> B4 (and git-patchwork-bot) try to deal with series revisions, but the process
> is not infallible due to needing to guess whether one series obsoletes another
> via weak string matches (subject + author). If v2 arrives with a modified
> subject than in v1 (even if it's a typo fix), or from a different email
> address, then auto-matching will fail.
>
> I would like to propose a "Superseded-by" follow-up trailer to help strengthen
> the link between series revisions. The trailer needs to be sent as a follow-up
> to the cover letter or first patch of the previous series.
>
> Superseded-by: [url-ending-with/message-id-of-next-version]
Could "Supercedes: [url]" posted with the new version work? -Alex
>
> Example:
>
> After submitting a new series revision, a contributor sends a follow-up email
> to the previous series submission, adding a single follow-up trailer, e.g.:
>
>
> Subject: Re: [PATCH v2 0/2] frobdrv: reduce frob latency
>
> [...]
> > Please submit a new revision that fixes this problem.
> >
> > Nacked-by: Maine Tainer <mtainer@example.com>
>
> Hi,
>
> I just submitted a v3 with these fixes.
>
> Superseded-by: https://lore.kernel.org/r/foo-bar-3333-1-git@example.net
>
> Of course, I don't expect a lot of folks to remember to do this, but I hope to
> incorporate this into the upcoming "auto-pr-exploder" tool that helps folks
> turn pull requests into well-formed patch series. In the same vein, when
> git-patchwork-bot recognizes that a series is superseded by a newer version,
> it can send an automated follow-up to the list to help indicate to the
> maintainer that a newer version of the patch/series is available.
>
> When b4 encounters this trailer, it can issue a warning to the maintainer that
> they aren't retrieving the latest series revision (and can automatically grab
> the new one if instructed to do so).
>
> Please let me know if this sounds reasonable.
>
> -K
>
next prev parent reply other threads:[~2021-04-13 20:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 20:49 RFC: Superseded-by: follow-up trailer Konstantin Ryabitsev
2021-04-13 20:53 ` Alex Elder [this message]
2021-04-13 21:02 ` Jason A. Donenfeld
2021-04-13 21:29 ` Steven Rostedt
2021-04-13 21:40 ` Konstantin Ryabitsev
2021-04-14 0:02 ` Steven Rostedt
2021-04-14 7:30 ` Peter Zijlstra
2021-04-14 11:49 ` Jason Gunthorpe
2021-04-14 13:57 ` James Bottomley
2021-04-14 14:36 ` Jason Gunthorpe
2021-04-14 14:56 ` Konstantin Ryabitsev
2021-04-14 15:57 ` Jason Gunthorpe
2021-04-14 17:07 ` Konstantin Ryabitsev
2021-04-14 17:24 ` Jason Gunthorpe
2021-04-14 17:40 ` Konstantin Ryabitsev
2021-04-14 18:46 ` Mark Brown
2021-04-14 18:58 ` Jason Gunthorpe
2021-04-14 15:01 ` Steven Rostedt
2021-04-14 15:36 ` Peter Zijlstra
2021-04-14 17:44 ` Willy Tarreau
2021-04-14 14:44 ` Theodore Ts'o
2021-04-14 18:51 ` Geert Uytterhoeven
2021-04-14 14:35 ` Konstantin Ryabitsev
2021-04-14 15:10 ` Peter Zijlstra
2021-04-14 12:52 ` Alex Elder
2021-04-13 21:04 ` Konstantin Ryabitsev
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=fd732fc9-83a9-5502-fba5-f08317bdcaf3@ieee.org \
--to=elder@ieee.org \
--cc=tools@linux.kernel.org \
--cc=users@linux.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 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.