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: Thu, 23 Mar 2023 11:24:23 -0600 [thread overview]
Message-ID: <87jzz7creg.fsf@meer.lwn.net> (raw)
In-Reply-To: <165bd284-580d-df03-ab04-f5214b1e6be4@leemhuis.info>
Thorsten Leemhuis <linux@leemhuis.info> writes:
> I currently can't really see the need for another book/top-level
> directory and to be honest it's by far my least favorite solution among
> the options on the table.
Well, it was just an idea that crossed my mind as I was thinking about
this stuff...it doesn't appear to have inspired a lot of enthusiasm. So
never mind that for now, I guess...I reserve the right to come back to
it in the future once we're getting overwhelmed by these things :)
> I'm taken back and forth between the other two options (e.g. put the
> text in Documentation/admin-guide/ or
> Documentation/admin-guide/tutorials/). Maybe I prefer the latter a
> little bit more.
Let's just put it in admin-guide, I guess, though the fit feels a bit
awkward. If we get more tutorials, we can make a separate section in
index.html, I don't think we need another subdirectory there at this
point.
Did you have further tweaks, or should I take v3?
Thanks,
jon
next prev parent reply other threads:[~2023-03-23 17:24 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
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 [this message]
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=87jzz7creg.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.