Linux Documentation
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: "ᴋᴀʀᴛɪᴋ sʜᴀʜ" <kartikpro9599@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] docs: improve introduction wording in howto.rst
Date: Sun, 7 Dec 2025 23:24:22 +0000	[thread overview]
Message-ID: <aTYMprKqrg-6lSP0@casper.infradead.org> (raw)
In-Reply-To: <CAOCmVvDcg9d0cNeGqH7+95Wffo4=WXUuSTR_Jbw_Swa3T8xOnQ@mail.gmail.com>

On Sun, Dec 07, 2025 at 03:07:43PM +0530, ᴋᴀʀᴛɪᴋ sʜᴀʜ wrote:
> -This is the be-all, end-all document on this topic.  It contains
> -instructions on how to become a Linux kernel developer and how to learn
> -to work with the Linux kernel development community.  It tries to not
> -contain anything related to the technical aspects of kernel programming,
> -but will help point you in the right direction for that.
> +This is a complete introductory document on this topic. It
> +contains instructions on how to become a Linux kernel developer
> +and how to work with the Linux kernel development community. It
> +does not cover the technical aspects of kernel programming, but
> +will help point you in the right direction for that.

I'd suggest following https://sembr.org/ for this paragraph since you're
editing it.  Don't go through and change the whole document.

Also, it is "the" complete document, not "a" complete document.

  parent reply	other threads:[~2025-12-07 23:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-07  9:37 [PATCH v4] docs: improve introduction wording in howto.rst ᴋᴀʀᴛɪᴋ sʜᴀʜ
2025-12-07 17:42 ` Randy Dunlap
2025-12-07 23:24 ` Matthew Wilcox [this message]
2025-12-07 23:41 ` Bagas Sanjaya
2025-12-08  2:11 ` Jonathan Corbet

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=aTYMprKqrg-6lSP0@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=kartikpro9599@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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