Re: [RFC PATCH v1 1/2] docs: reporting-issue: rework the detailed guide

[Jonathan Corbet <corbet@lwn.net>]

Thorsten Leemhuis <linux@leemhuis.info> writes:

> Rework the detailed step-by-step guide for various reasons:
>
> * Simplify the search with the help of lore.kernel.org/all/, which did
>   not exist when the text was written.
>
> * Make use of the recently added document
>   Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst,
>   which covers many steps this text partly covered way better.
>
> * The 'quickly report a stable regression to the stable team' approach
>   hardly worked out: most of the time the regression was not known yet.
>   Try a different approach using the regressions list.
>
> * Reports about stable/longterm regressions most of the time were
>   greeted with a brief reply along the lines of 'Is mainline affected as
>   well?'; this is needed to determine who is responsible, so we might as
>   well make the reporter check that before sending the report (which
>   verify-bugs-and-bisect-regressions.rst already tells them to do, too).
>
> * A lot of fine tuning after seeing what people were struggling with.

So I have read through this, and don't find anything objectionable.  I
will point out that each of those bullet items above might be better
handled in a separate patch; the result might be easier to review.

Thanks,

jon