On Wed, 29 Mar 2023 11:04:01 +0200 Thorsten Leemhuis wrote:

FWIW, I see how this is well meant, but I'm not really happy with the
last sentence, as one of the problems I notice when handling regression
is: it sometimes takes weeks to get regressions fixed that could have
been solved quickly by reverting the culprit (and reapplying an improved
version of the change or the change together and a fix later). That's
why Documentation/process/handling-regressions.rst strongly suggest to
revert changes that cause regressions if the problem can't be fixed
quickly -- especially if the change made it into a proper release. The
two texts thus now not slightly contradict each other.

I noticed that this change was already applied, but how would you feel
about changing the second sentence into something like this maybe?

Please escalate the cases which can be fixed by easy reverts because 
I can't think of any in networking :(

The entire doc is based on our painful experience telling people the
same thing over and over again, we don't want to include things which
don't actually happen on netdev. Longer the doc is the less likely
people will actually read it :(