Re: RFC: Superseded-by: follow-up trailer

From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	Alex Elder <elder@ieee.org>,
	users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: RFC: Superseded-by: follow-up trailer
Date: Tue, 13 Apr 2021 17:40:31 -0400	[thread overview]
Message-ID: <20210413214031.fenjvgh5helyuqdz@nitro.local> (raw)
In-Reply-To: <20210413172901.1465307c@gandalf.local.home>

On Tue, Apr 13, 2021 at 05:29:01PM -0400, Steven Rostedt wrote:
> Now, I would really like the Supercedes: tag, as its just a link you need,
> and not a email sent. Ideally this would be in all the patches (with a
> direct link to what it Supercedes. I may update my scripts to do exactly
> this, as I always add a "Link: " to the last version, and that's in my
> repo. Or perhaps b4 could add this too!

I'd rather folks used the following notation in the cover letter/patch
basement:

    Previous versions:

    Link: https://lore.kernel.org/r/foo # v2
    Link: https://lore.kernel.org/r/bar # v1

This is much more succinct, indicates the version number in the trailer, and
removes the need to remember how to spell "Superseded", as there seems to be
little consensus. :)

The tooling on the kernel.org side can automatically send the required
follow-ups to previous threads when it finds these trailers in newer
submissions.

-K