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 v1] docs: verify/bisect: fixes, finetuning, and support for Arch
Date: Thu, 07 Mar 2024 04:40:12 -0700 [thread overview]
Message-ID: <87o7bqjmn7.fsf@meer.lwn.net> (raw)
In-Reply-To: <6592c9ef4244faa484b4113f088dbc1beca61015.1709716794.git.linux@leemhuis.info>
Thorsten Leemhuis <linux@leemhuis.info> writes:
> Assorted changes for the recently added document.
>
> Improvements:
>
> * Add instructions for installing required software on Arch Linux.
>
> Fixes:
>
> * Move a 'git remote add -t master stable [...]' from a totally wrong
> to the right place.
>
> * Fix two anchors.
>
> * Add two required packages to the openSUSE install instructions.
>
> Fine tuning:
>
> * Improve the reference section about downloading Linux mainline sources
> to make it more obvious that those are alternatives.
>
> * Include the full instructions for git bundles to ensure the remote
> gets the right name; that way the text also works stand alone.
>
> * Install ncurses and qt headers for use of menuconfig and xconfig by
> default, but tell users that they are free to omit them.
>
> * Mention ahead of time which version number are meant as example in
> commands used during the step-by-step guide.
>
> * Mention that 'kernel-install remove' might do a incomplete job.
>
> Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
> ---
>
> Lo! A quick note reg "mention ahead of time which version numbers are
> meant as example in commands used during the step-by-step guide". I did
> that, as I've seen someone following the guide without replacing the
> version numbers, so pointing this out with a few words seemed wise. But
> I'm not sure if the way I did it was the best; if someone has a better
> idea how to do that, please let me know. Ciao, Thorsten
> ---
> .../verify-bugs-and-bisect-regressions.rst | 135 +++++++++++-------
> 1 file changed, 84 insertions(+), 51 deletions(-)
No better ideas...I've applied this, thanks.
jon
prev parent reply other threads:[~2024-03-07 11:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 9:21 [PATCH v1] docs: verify/bisect: fixes, finetuning, and support for Arch Thorsten Leemhuis
2024-03-06 10:18 ` Petr Tesařík
2024-03-06 10:34 ` Thorsten Leemhuis
2024-03-06 13:27 ` Bagas Sanjaya
2024-03-07 8:56 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-09 6:54 ` Bagas Sanjaya
2024-03-07 11:40 ` 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=87o7bqjmn7.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 NNTP newsgroup(s).