From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>,
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: Wed, 15 Mar 2023 11:17:33 +0700 [thread overview]
Message-ID: <ZBFG3UqcS7IhGP6t@debian.me> (raw)
In-Reply-To: <87a60frxk0.fsf@meer.lwn.net>
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
On Tue, Mar 14, 2023 at 12:35:11PM -0600, Jonathan Corbet wrote:
> 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.
>
I think so, but I guess "web-oriented" means doing a lot of searching
the Internet to accomplish kernel-related tasks, right?
For the initial tutorial contents, I'd like to see:
* this one (for end users and tester)
* kernel building with development environment setup and
patch submission (for developers)
* kernel bisection (as in v1)
* reporting bugs (tldr: make sure to include info as detail as you can
get and Cc: related mailing lists [scripts/get_maintainer.pl
helps]).
Other tutorial-style docs across Documentation/ can be candidate of
moving to Documentation/tutorials/.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-03-15 4:17 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
2023-03-15 4:17 ` Bagas Sanjaya [this message]
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=ZBFG3UqcS7IhGP6t@debian.me \
--to=bagasdotme@gmail.com \
--cc=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.