[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZA1X46ClAJGc/2V7@1wt.eu>
Date: Sun, 12 Mar 2023 05:41:07 +0100
From: Willy Tarreau <w@....eu>
To: David Laight <David.Laight@...LAB.COM>
Cc: "'Sasha Levin'" <sashal@...nel.org>,
Matthew Wilcox <willy@...radead.org>,
Eric Biggers <ebiggers@...nel.org>,
Pavel Machek <pavel@....cz>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>,
"viro@...iv.linux.org.uk" <viro@...iv.linux.org.uk>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>
Subject: Re: AUTOSEL process
On Sat, Mar 11, 2023 at 10:38:10PM +0000, David Laight wrote:
> ...
> > I suppose that if I had a way to know if a certain a commit is part of a
> > series, I could either take all of it or none of it, but I don't think I
> > have a way of doing that by looking at a commit in Linus' tree
> > (suggestions welcome, I'm happy to implement them).
>
> Could something in git (eg when patches get applied) add dependencies
> between the patches in a series.
> While that won't force the entire series be added, it would ensure
> that all earlier patches are added.
I suspect that having an option to keep the message ID in the footer (a
bit like the "cherry-picked from" tag but instead "blongs to series")
could possibly help. And when no such info is present we could have
one ID generated per "git am" execution since usually if you apply an
mbox, it constitutes a series (but not always of course, though it's
not difficult to arrange series like this).
Willy
Powered by blists - more mailing lists