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

[Peter Zijlstra <peterz@infradead.org>]

On Tue, Apr 13, 2021 at 05:40:31PM -0400, Konstantin Ryabitsev wrote:
> 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. :)

How would you handle the difference between the above and:

Depends on:

Link: https://lkml.kernel.org/r/foo

Which is also a semi common thing to do with larger work that comes in
multiple dependent series.

That is; I supppse; a long winded way of saying that for parsing (both
human and machine) it might be useful to have distinct tag names. Now I
agree with you that Supersedes is a crap word to spell, but it has the
distinction of being clear on intent.

So my 2ct go to adding Supercedes: and Depends-on:

(Alternatively, Replaces: ?)