From: "Theodore Ts'o" <tytso@mit.edu>
To: Josh Marshall <joshua.r.marshall.1991@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
"Bilbao, Carlos" <carlos.bilbao@amd.com>, ngn <ngn@ngn.tf>,
linux-newbie@vger.kernel.org,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
pranjal.singh4370@gmail.com, "bilbao@vt.edu" <bilbao@vt.edu>
Subject: Re: Feedback on my development setup
Date: Thu, 25 Apr 2024 16:14:27 -0400 [thread overview]
Message-ID: <20240425201427.GC3749403@mit.edu> (raw)
In-Reply-To: <CAFkJGRf+K7iGY+TJQu3RDuUv_Xna4BMZmEfeuhHJ0JPg3KQmTg@mail.gmail.com>
On Thu, Apr 25, 2024 at 01:08:36PM -0400, Josh Marshall wrote:
>
> I cannot abide by this. Not out of obstinance. This document is not
> written for a veteran. It probably isn't even written for anyone on
> this list. It is meant to be much more approachable than that.
> Comparing to the closest existing document at
> https://docs.kernel.org/dev-tools/gdb-kernel-debugging.html , the
> difference in intended audience and skill level is stark. Let alone
> being able to find that document since it is so buried relative to the
> intent of someone trying to get started. I have heard several times "
> you should rather improve existing docs" but without really breaking
> into all the implications that 'just' doesn't help. Given the back
> and forth required to express the finesse here, I am willing to have a
> phone or video call to get this right.
Just as there are dozens of git tutorials which are floating around
the web which are separate from the official git documentation, if
what you want is to have an unofficial document designed for a
specific audience which is not the "vetran", that's totally fine.
Perhaps you can work with the kernel newbies folks, and look at
joining forces with their documentation, e.g.:
https://kernelnewbies.org/FirstKernelPatch
The benefit of joining forces with them might be that more people will
see your document. A random gitlab page is not going to be as
discoverable.
So I think there may be some crosstalk because your goals might not be
what others have been assuming your goals to be. If you want to have
your own unofficial kernel tutorial, have at it! You don't need to
get permission from anyone else, and you don't need to engage with the
community on this mailing list or anywhere else.
The flip side is if you want to get input from this community, you may
find that you are more likely to get that help if you are discussing
things on the mailing list, as opposed to expecting us to go find your
gitlab site and participating there. We can't force you to use
mailing list threads; but at the same time, your expecting to us to
use gitlab might not be very fruitful.
Best regards,
- Ted
next prev parent reply other threads:[~2024-04-25 20:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFkJGRc824vYEufG=6ZVPAW2iVpd0NDThJadZVrUk_ZND_qJag@mail.gmail.com>
[not found] ` <Zh6Xbqijp8rRGo1H@archbtw>
[not found] ` <CAFkJGRe+UpNPSnSL623o6G+NCkK_uGPx-NCNLQx0vSGpMo98eg@mail.gmail.com>
[not found] ` <CAPzh0z8RySn429XYQHoP_c9UA+pb6SLHGhH40vQDhc3P2xiysQ@mail.gmail.com>
[not found] ` <CAFkJGRfK=1f8tfWO8G0v8SOmCwCgK7P5y7g2My47VG6Obb1DNw@mail.gmail.com>
[not found] ` <ZiE9ydgMtpKOBLDk@archbtw>
[not found] ` <CAFkJGRddGHK0j4CcQUoRKiD3afniLY=rRV5npY5wpauqqY0XZg@mail.gmail.com>
[not found] ` <CAFkJGRdFuMoO4_mR-cR1NWjKQJnopN0v1R11-jSnLn+FKcOCdg@mail.gmail.com>
[not found] ` <CAFkJGRcg+ThJ-xUve0=WorChW=-6PreLHXeM8YwtwzwpkHTu8g@mail.gmail.com>
[not found] ` <CAFkJGRcgJA4qe1AVi23ZQVPr_UEzkTBPH8f30g=OsKmii7QzQw@mail.gmail.com>
[not found] ` <ZiKYXX-v0Eu-qCBt@archbtw>
[not found] ` <CAFkJGRdjvebW6u6pyyA_MeHsoecRgYjiVrxoWYWsREdYH9iOFQ@mail.gmail.com>
2024-04-23 16:39 ` Feedback on my development setup 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 [this message]
2024-04-25 20:02 ` Theodore Ts'o
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=20240425201427.GC3749403@mit.edu \
--to=tytso@mit.edu \
--cc=bilbao@vt.edu \
--cc=carlos.bilbao@amd.com \
--cc=corbet@lwn.net \
--cc=joshua.r.marshall.1991@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-newbie@vger.kernel.org \
--cc=ngn@ngn.tf \
--cc=pranjal.singh4370@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).