From: Peter Zijlstra <peterz@infradead.org>
To: 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 17:10:41 +0200 [thread overview]
Message-ID: <YHcF8YE2BNjUvmL/@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20210414143504.l3txdpd6xbcf6qh5@nitro.local>
On Wed, Apr 14, 2021 at 10:35:04AM -0400, Konstantin Ryabitsev wrote:
> Hmm... there is an officially sanctioned way to indicate patch
> interdependencies using "prerequisite-patch-id:" footers (see
> https://git-scm.com/docs/git-format-patch#_base_tree_information).
>
> That said, I've never seen anyone actually use them, I guess for two reasons:
>
> 1. it's per-patch, not per-series
> 2. it requires running "git patch-id" on each patch in the dependencies
I'm not using git, not for making patches, not for sending patches, and
reading this thread makes me glad I'm not. It looks super painful in all
respects.
As to the original proposal, I'm with Steve, I'd never bother to dig out
the old thread (in fact, it's not even in my Sent folder).
As to the pain mentioned elsewhere, I'm not having that, I have an mbox
of the old submission laying about that I use as a basis for the new
submission, so I have all Msg-IDs right there.
Maybe the new-fangled tool you all need on the submission side already
exists, it's called quilt :-)
next prev parent reply other threads:[~2021-04-14 15:12 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
2021-04-14 18:51 ` Geert Uytterhoeven
2021-04-14 14:35 ` Konstantin Ryabitsev
2021-04-14 15:10 ` Peter Zijlstra [this message]
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=YHcF8YE2BNjUvmL/@hirez.programming.kicks-ass.net \
--to=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).