mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <linux@leemhuis.info>
To: Jonathan Corbet <corbet@lwn.net>
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: [PATCH v1 0/3] docs: verify/bisect: fine tuning, testing fixes, and using a build host
Date: Mon,  1 Apr 2024 11:29:40 +0200	[thread overview]
Message-ID: <cover.1711963460.git.linux@leemhuis.info> (raw)

A quick series with various improvements for
Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst.

* The first patch contains various fixes and some fine tuning.

* The second adds a few 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 third 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.
---

Hi! While at it let me mention one more thing unrelated to the changes
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; but I can split this up if the two latter patches better
should go into -next.

Thorsten Leemhuis (3):
  docs: verify/bisect: git switch; proper headlines; various fixes;
  docs: verify/bisect: explain testing reverts, patches and newer code
  docs: verify/bisect: describe how to use a build host

 .../verify-bugs-and-bisect-regressions.rst    | 469 +++++++++++++-----
 1 file changed, 344 insertions(+), 125 deletions(-)


base-commit: b8cfda5c9065cd619a97c17da081cbfab3b1e756
-- 
2.44.0


             reply	other threads:[~2024-04-01  9:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01  9:29 Thorsten Leemhuis [this message]
2024-04-01  9:29 ` [PATCH v1 1/3] docs: verify/bisect: git switch; proper headlines; various fixes; Thorsten Leemhuis
2024-04-01  9:29 ` [PATCH v1 2/3] docs: verify/bisect: explain testing reverts, patches and newer code Thorsten Leemhuis
2024-04-01  9:29 ` [PATCH v1 3/3] docs: verify/bisect: describe how to use a build host Thorsten Leemhuis
2024-04-05 10:22 ` [PATCH v1 0/3] docs: verify/bisect: fine tuning, testing fixes, and using " Linux regression tracking (Thorsten Leemhuis)

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=cover.1711963460.git.linux@leemhuis.info \
    --to=linux@leemhuis.info \
    --cc=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

Powered by JetHome