From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Manuel Ebner <manuelebnerli@mailbox.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: doc-guide: improve language
Date: Mon, 16 Nov 2026 06:27:56 +0700 [thread overview]
Message-ID: <avo_9xmBYyPpAUZ0@archie.me> (raw)
In-Reply-To: <20261115210423.1089716-2-manuelebnerli@mailbox.org>
[-- Attachment #1: Type: text/plain, Size: 858 bytes --]
On Sun, Nov 15, 2026 at 10:04:23PM +0100, Manuel Ebner wrote:
> This guide is for contributors who would like to improve that situation.
> Kernel documentation improvements can be made by developers at a variety of
> -skill levels; they are a relatively easy way to learn the kernel process in
> -general and find a place in the community. The bulk of what follows is the
> -documentation maintainer's list of tasks that most urgently need to be
> -done.
> +skill levels; they are a relatively easy way to learn the kernel contribution
> +process in general and find a place in the community. The bulk of what
> +follows is the documentation maintainer's list of tasks that most urgently
> +need to be done.
Looks good, thanks!
Acked-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-11-15 23:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-15 21:04 Manuel Ebner
2026-11-15 23:27 ` Bagas Sanjaya [this message]
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=avo_9xmBYyPpAUZ0@archie.me \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manuelebnerli@mailbox.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®