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
In-Reply-To: <1a788a8e7ba8a2063df08668f565efa832016032.1678021408.git.linux@leemhuis.info>
References: <1a788a8e7ba8a2063df08668f565efa832016032.1678021408.git.linux@leemhuis.info>
Date:   Tue, 14 Mar 2023 12:35:11 -0600
Message-ID: <87a60frxk0.fsf@meer.lwn.net>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk

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