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
next prev parent reply other threads:[~2021-04-13 21:40 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
2021-04-13 21:02 ` Jason A. Donenfeld
2021-04-13 21:29 ` Steven Rostedt
2021-04-13 21:40 ` Konstantin Ryabitsev [this message]
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=20210413214031.fenjvgh5helyuqdz@nitro.local \
--to=konstantin@linuxfoundation.org \
--cc=Jason@zx2c4.com \
--cc=elder@ieee.org \
--cc=rostedt@goodmis.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.