From: Bagas Sanjaya <bagasdotme@gmail.com>
To: linux-doc@vger.kernel.org
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>, kernel-janitors@vger.kernel.org
Subject: MAINTAINERS improv suggestion
Date: Thu, 21 Jul 2022 16:05:57 +0700 [thread overview]
Message-ID: <YtkW9awXT3nWyvts@debian.me> (raw)
Hi Lukas and everyone in linux-doc ML,
Thanks for your work on doc cleanup. However, there's still one thing left:
MAINTAINERS. The patch submitters tips, IMO, need some work.
Here's my notes:
* Nowadays most drivers (especially on embedded architectures like Arm) were
initially developed out-of-tree, then follows mainline inclusion process
But the second item read "Try to release a few ALPHA test versions to the
net. Announce them onto the kernel channel and await results". These
drivers were submitted not as ALPHA-grade, but near-production grade.
* The fifth item mentioned using `diff -u` to generate patches, however
since 9f364b605f34e1 ("submitting-patches.rst: presume git will be used"),
the documentation elsewhere assumed git would be used.
Thanks.
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2022-07-21 9:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 9:05 Bagas Sanjaya [this message]
2022-07-21 10:02 ` MAINTAINERS improv suggestion Lukas Bulwahn
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=YtkW9awXT3nWyvts@debian.me \
--to=bagasdotme@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=lukas.bulwahn@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 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.