From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "ᴋᴀʀᴛɪᴋ sʜᴀʜ" <kartikpro9599@gmail.com>, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] docs: improve introduction wording in howto.rst
Date: Mon, 8 Dec 2025 06:41:46 +0700 [thread overview]
Message-ID: <aTYQus43mIbI2CoS@archie.me> (raw)
In-Reply-To: <CAOCmVvDcg9d0cNeGqH7+95Wffo4=WXUuSTR_Jbw_Swa3T8xOnQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]
On Sun, Dec 07, 2025 at 03:07:43PM +0530, ᴋᴀʀᴛɪᴋ sʜᴀʜ wrote:
> >From 56985c72f365c7f0e9ba8ae66ba99c198c15128c Mon Sep 17 00:00:00 2001
> From: kartikpro9599-hash <kartikpro9599@gmail.com>
> Date: Sun, 7 Dec 2025 13:53:02 +0530
> Subject: [PATCH v4] docs: improve introduction wording in howto.rst
>
> Signed-off-by: kartikpro9599-hash <kartikpro9599@gmail.com>
Please add patch description and also make sure that From: and Signed-off-by:
identities match (or pass --from to git-format-patch(1) if it isn't the case).
> -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.
So basically s/be-all, end-all/a complete/, right?
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-12-07 23:41 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
2025-12-07 23:41 ` Bagas Sanjaya [this message]
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=aTYQus43mIbI2CoS@archie.me \
--to=bagasdotme@gmail.com \
--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