[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZAzh7l8qWtkeh/KK@sol.localdomain>
Date: Sat, 11 Mar 2023 12:17:50 -0800
From: Eric Biggers <ebiggers@...nel.org>
To: Sasha Levin <sashal@...nel.org>
Cc: Theodore Ts'o <tytso@....edu>,
Matthew Wilcox <willy@...radead.org>,
Pavel Machek <pavel@....cz>, linux-kernel@...r.kernel.org,
stable@...r.kernel.org, viro@...iv.linux.org.uk,
linux-fsdevel@...r.kernel.org
Subject: Re: AUTOSEL process
On Sat, Mar 11, 2023 at 01:26:57PM -0500, Sasha Levin wrote:
> I'm getting a bunch of suggestions and complaints that I'm not implementing
> those suggestions fast enough on my spare time.
BTW, the "I don't have enough time" argument is also a little frustrating
because you are currently insisting on doing AUTOSEL at all, at the current
sensitivity that picks up way too many commits. I can certainly imagine that
that uses a lot of your time! But, many contributors are telling you that
AUTOSEL is actually *worse than nothing* currently.
So to some extent this is a self-inflicted problem. You are *choosing* to spend
your precious time running in-place with something that is not working well,
instead of putting AUTOSEL on pause or turning down the sensitivity to free up
time while improvements to the process are worked on.
(And yes, I know there are many stable patches besides AUTOSEL, and it's a lot
of work, and I'm grateful for what you do. I am *just* talking about AUTOSEL
here. And yes, I agree that AUTOSEL is needed in principle, so there's no need
to re-hash the arguments for why it exists. It just needs some improvements.)
- Eric
Powered by blists - more mailing lists