From: "Theodore Ts'o" <tytso@mit.edu>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
"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: Wed, 14 Apr 2021 10:44:00 -0400 [thread overview]
Message-ID: <YHb/sM95npXrwKPJ@mit.edu> (raw)
In-Reply-To: <20210414114950.GM227011@ziepe.ca>
On Wed, Apr 14, 2021 at 08:49:50AM -0300, Jason Gunthorpe wrote:
>
> v3:
> - blah blah
> v2: https://lore.kernel.org/r/foo
> - blah blah
> v1: https://lore.kernel.org/r/bar
> b4 does a nice job helping the maintainer, but the submitter has no
> helpful common tooling currently.
It would be nice (and I think possible) if finding the mapping between
v1 and https://lore.kernel.org/r/bar could be automated --- and if we
had an appropriate hook in git send-email, it should be possible to
capture the message-id and stash it in a state file somewhere so the
developer could either fetch it manually, or if we had something like
debian's "debchange" command to make it easy to compose the changelog,
it could fetch it and stash it into the template file before opening
up an editor for the developer to update the changelog.
What do folks think?
- Ted
next prev parent reply other threads:[~2021-04-14 14:46 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
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 [this message]
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=YHb/sM95npXrwKPJ@mit.edu \
--to=tytso@mit.edu \
--cc=Jason@zx2c4.com \
--cc=elder@ieee.org \
--cc=jgg@ziepe.ca \
--cc=peterz@infradead.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.