All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	regressions@lists.linux.dev
Subject: Re: [PATCH v3] docs: describe how to quickly build a trimmed kernel
Date: Tue, 14 Mar 2023 12:35:11 -0600	[thread overview]
Message-ID: <87a60frxk0.fsf@meer.lwn.net> (raw)
In-Reply-To: <1a788a8e7ba8a2063df08668f565efa832016032.1678021408.git.linux@leemhuis.info>

Thorsten Leemhuis <linux@leemhuis.info> writes:

> Add a text explaining how to quickly build a kernel, as that's something
> users will often have to do when they want to report an issue or test
> proposed fixes.

So I think the time has come to apply this.  I did have one final
thought, though...  In the v2 discussion, you said:

> Be warned, if it works I might do the same for "reporting issues". ;)
> But let's first see how this goes (and if we get any feedback to be able
> to tell if this experiment worked).

This caused me to wonder if we shouldn't create a new book called
"tutorials" for this kind of stuff, with an explicit proviso that a more
web-oriented approach is OK in that section?  Tutorial documentation
*is* quite different from reference material, but we've really made no
effort to treat the two differently so far.

Thoughts?

Thanks,

jon

  parent reply	other threads:[~2023-03-14 18:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-05 13:04 [PATCH v3] docs: describe how to quickly build a trimmed kernel Thorsten Leemhuis
2023-03-06  4:14 ` Bagas Sanjaya
2023-03-06  6:03   ` Thorsten Leemhuis
2023-03-06  4:19 ` Bagas Sanjaya
2023-03-06  5:40   ` Thorsten Leemhuis
2023-03-06  8:57     ` Bagas Sanjaya
2023-03-06  9:07       ` Thorsten Leemhuis
2023-03-07  2:57         ` Bagas Sanjaya
2023-03-09 14:42 ` Greg KH
2023-03-14 18:35 ` Jonathan Corbet [this message]
2023-03-15  4:17   ` Bagas Sanjaya
2023-03-15  9:28   ` Thorsten Leemhuis
2023-03-16 18:27     ` Jonathan Corbet
2023-03-22 13:47       ` Thorsten Leemhuis
2023-03-23 17:24         ` Jonathan Corbet
2023-03-23 17:37           ` Thorsten Leemhuis
2023-03-23 18:08             ` Jonathan Corbet
2023-03-15  4:19 ` Bagas Sanjaya

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=87a60frxk0.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=lukas.bulwahn@gmail.com \
    --cc=rdunlap@infradead.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.