From: Pranjal Singh <pranjal.singh4370@gmail.com>
To: Josh Marshall <joshua.r.marshall.1991@gmail.com>, ngn <ngn@ngn.tf>
Cc: linux-newbie@vger.kernel.org
Subject: Re: Feedback on my development setup
Date: Tue, 23 Apr 2024 21:38:18 +0530 [thread overview]
Message-ID: <eeede97e-3330-4613-b0b8-9fae99fe2b50@gmail.com> (raw)
In-Reply-To: <CAFkJGRdjvebW6u6pyyA_MeHsoecRgYjiVrxoWYWsREdYH9iOFQ@mail.gmail.com>
On 23/04/24 21:04, Josh Marshall wrote:
> I have a draft document which I would like broader review on, which
> currently lives here:
> https://gitlab.com/anadon/getting-started-on-kernel-dev-guide-workspace.
> This document is to ease the setup of Kernel Development. I intend to
> send this in as a patch to the mainline doc tree once it gets by a
> suitable number of reviewers.
Hi Josh,
Commendable effort.
I find the doc a little verbose: The official documentation, (for better
or worse) doesn't explain things in such detail, and assumes
considerable maturity in OSs and the shell.
For instance, the paragraph in the beginning doesn't give a crisp
description of what's going on - I think you can split it into two. "It
uses as an example..." can go to the end. Same goes for the first note:
are all of the details even needed?
The later sections are user-manual-y: "Here we need to obtain the basic
materials to work with. These are ..." can be "Download a VM image and
the Linux source."
Unrelated: a mistake I made many times when compiling Linux was to go
with [Y]s and [n]s - it may be worth mentioning in that section that
some prompts take an empty string for an answer, at least in Debian/Ubuntu.
Disclaimer: Linux Newbie here. Suggestions/disagreement will make my day.
Thanks,
Pranjal
next prev parent reply other threads:[~2024-04-23 16:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 12:38 Feedback on my development setup Josh Marshall
2024-04-16 14:56 ` ngn
2024-04-16 15:03 ` Josh Marshall
2024-04-16 15:21 ` ngn
2024-04-17 16:11 ` Josh Marshall
[not found] ` <CAPzh0z8RySn429XYQHoP_c9UA+pb6SLHGhH40vQDhc3P2xiysQ@mail.gmail.com>
2024-04-17 21:18 ` Josh Marshall
2024-04-18 15:35 ` ngn
2024-04-18 19:15 ` Josh Marshall
2024-04-18 19:27 ` Josh Marshall
2024-04-18 19:52 ` Josh Marshall
2024-04-18 21:40 ` Josh Marshall
2024-04-19 16:14 ` ngn
2024-04-23 15:34 ` Josh Marshall
2024-04-23 16:08 ` Pranjal Singh [this message]
2024-04-23 16:39 ` Bilbao, Carlos
2024-04-23 17:43 ` Josh Marshall
2024-04-25 5:37 ` Josh Marshall
2024-04-25 14:36 ` Bilbao, Carlos
2024-04-25 14:54 ` Josh Marshall
2024-04-25 15:14 ` Jonathan Corbet
[not found] ` <CAFkJGReoq2s+LR1kj1hj8QvsKsEhk+CLYtCXV=DQTjTqan3DOg@mail.gmail.com>
2024-04-25 16:59 ` Carlos Bilbao
2024-04-25 17:08 ` Josh Marshall
2024-04-25 20:14 ` Theodore Ts'o
2024-04-25 20:02 ` Theodore Ts'o
2024-04-25 14:32 ` Thomas Bertschinger
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=eeede97e-3330-4613-b0b8-9fae99fe2b50@gmail.com \
--to=pranjal.singh4370@gmail.com \
--cc=joshua.r.marshall.1991@gmail.com \
--cc=linux-newbie@vger.kernel.org \
--cc=ngn@ngn.tf \
/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.