[PATCH v2 0/5] docs: reporting-issues: tweak a few areas and rewrite the ending

Thorsten Leemhuis posted 5 patches 2 weeks, 6 days ago
Only 0 patches received!
.../quickly-build-trimmed-linux.rst           |  14 +-
.../admin-guide/reporting-issues.rst          | 210 +++++++++---------
.../verify-bugs-and-bisect-regressions.rst    |  15 +-
3 files changed, 123 insertions(+), 116 deletions(-)
[PATCH v2 0/5] docs: reporting-issues: tweak a few areas and rewrite the ending
Posted by Thorsten Leemhuis 2 weeks, 6 days ago
This patch-set tweaks a few parts in the fringes of our text on bug
reporting while replacing two sections at the end with a new text as
proper appendix that hopefully better fits the purpose and covers more
aspects.

This is the first versions of this patch-set, but it starts as v2, as it
contains three patches and a few bits that were part of an earlier and
bigger patch-set. This incorporates review feedback given there. The
last patch in this series is mostly new, but includes a few bits from
patch 4 and 5 of the earlier series.

Ciao, Thorsten

v2:
- initial version with 3 patches taken from this abandoned patch-set:
  https://lore.kernel.org/all/cover.1761481839.git.linux@leemhuis.info/
- Rewrite the section at the end and make it a proper appendix; based
  on patches 4 and 5 from above patch-set
- Incorporate various mostly minor review feedback. Among them:
  - Drop the change switching from single to double quotes.
  - Point out that feedback can be sent as a patch, too – and add a
    patch to sync the text about feedback with two other documents that
    contain a para which this section is based on.

Thorsten Leemhuis (5):
  docs: reporting-issues: mention text is best viewed rendered
  docs: reporting-issues: tweak the reference section intro
  docs: reporting-issues: add conclusion to the step-by-step guide
  docs: verify-bugs-… and quickly-build-…: improve feedback section
  docs: reporting-issues: create a proper appendix explaining
    specialties

 .../quickly-build-trimmed-linux.rst           |  14 +-
 .../admin-guide/reporting-issues.rst          | 210 +++++++++---------
 .../verify-bugs-and-bisect-regressions.rst    |  15 +-
 3 files changed, 123 insertions(+), 116 deletions(-)


base-commit: 73f175a46330c57ab5797287233cbf83a36b6a99
-- 
2.53.0

Re: [PATCH v2 0/5] docs: reporting-issues: tweak a few areas and rewrite the ending
Posted by Jonathan Corbet 2 weeks, 6 days ago
Thorsten Leemhuis <linux@leemhuis.info> writes:

> This patch-set tweaks a few parts in the fringes of our text on bug
> reporting while replacing two sections at the end with a new text as
> proper appendix that hopefully better fits the purpose and covers more
> aspects.
>
> This is the first versions of this patch-set, but it starts as v2, as it
> contains three patches and a few bits that were part of an earlier and
> bigger patch-set. This incorporates review feedback given there. The
> last patch in this series is mostly new, but includes a few bits from
> patch 4 and 5 of the earlier series.

I don't see anything to complain about here ... if nobody screams, I'll
apply them in a few days or so.

Thanks,

jon
Re: [PATCH v2 0/5] docs: reporting-issues: tweak a few areas and rewrite the ending
Posted by Jonathan Corbet 2 weeks, 1 day ago
Jonathan Corbet <corbet@lwn.net> writes:

> Thorsten Leemhuis <linux@leemhuis.info> writes:
>
>> This patch-set tweaks a few parts in the fringes of our text on bug
>> reporting while replacing two sections at the end with a new text as
>> proper appendix that hopefully better fits the purpose and covers more
>> aspects.
>>
>> This is the first versions of this patch-set, but it starts as v2, as it
>> contains three patches and a few bits that were part of an earlier and
>> bigger patch-set. This incorporates review feedback given there. The
>> last patch in this series is mostly new, but includes a few bits from
>> patch 4 and 5 of the earlier series.
>
> I don't see anything to complain about here ... if nobody screams, I'll
> apply them in a few days or so.

...and I have now done that, thanks.

jon