From: Jonathan Corbet <corbet@lwn.net>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: regressions@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Bagas Sanjaya" <bagasdotme@gmail.com>,
"Petr Tesařík" <petr@tesarici.cz>
Subject: Re: [PATCH v2 0/6] docs: verify/bisect: fine tuning, testing fixes, build host, order
Date: Mon, 15 Apr 2024 10:01:55 -0600 [thread overview]
Message-ID: <87bk6awr64.fsf@meer.lwn.net> (raw)
In-Reply-To: <cover.1712647788.git.linux@leemhuis.info>
Thorsten Leemhuis <linux@leemhuis.info> writes:
> A quick series with various improvements for
> Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst after
> receiving feedback on the text or seeing people struggle with certain
> tasks.
>
> * The first two patches contains various fixes and some fine tuning.
>
> * The third is mainly a layout improvement that results in a somewhat
> large patch.
>
> * The fourth adds instructions for later testing of reverts, fixes, or
> newer versions. This was already hinted at; but during some early
> work on Documentation/admin-guide/reporting-issues.rst to better
> reconcile the two it seemed wise to cover this properly here.
>
> * The fifth patch briefly outlines how to build kernels on a different
> host; it came into being after a second user within one week asked for
> this. That also allowed the text to briefly cover cross-compilation.
>
> * The sixth makes users that face a regression within a stable series
> test that series first before they are told to test mainline.
> ---
>
> Hi! While at it let me mention one more thing unrelated to the changes
> that came up where I'm unsure if the current approach by the text was
> a wise choice:
>
> * Should the document tell users to avoid mainline during merge windows?
>
> Some input from the community on this would be splendid.
>
> Ciao, Thorsten
>
> P.S.: Not totally sure, but I think this should go into 6.9 as this is
> a new document; if not I guess it would be wise to pick the first two,
> as they fix bugs.
Nobody seems to be complaining, so I've gone ahead and applied the set
to docs-fixes.
Thanks,
jon
prev parent reply other threads:[~2024-04-15 16:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 7:30 [PATCH v2 0/6] docs: verify/bisect: fine tuning, testing fixes, build host, order Thorsten Leemhuis
2024-04-09 7:30 ` [PATCH v2 1/6] docs: verify/bisect: use git switch, tag kernel, and various fixes Thorsten Leemhuis
2024-04-09 7:30 ` [PATCH v2 2/6] docs: verify/bisect: add and fetch stable branches ahead of time Thorsten Leemhuis
2024-04-09 7:30 ` [PATCH v2 3/6] docs: verify/bisect: proper headlines and more spacing Thorsten Leemhuis
2024-04-09 7:30 ` [PATCH v2 4/6] docs: verify/bisect: explain testing reverts, patches and newer code Thorsten Leemhuis
2024-04-09 7:30 ` [PATCH v2 5/6] docs: verify/bisect: describe how to use a build host Thorsten Leemhuis
2024-04-09 7:30 ` [PATCH v2 6/6] docs: verify/bisect: stable regressions: first stable, then mainline Thorsten Leemhuis
2024-04-15 16:01 ` Jonathan Corbet [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bk6awr64.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=bagasdotme@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=petr@tesarici.cz \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).