From: Randy Dunlap <rdunlap@infradead.org>
To: Jakub Kicinski <kuba@kernel.org>, corbet@lwn.net
Cc: linux-doc@vger.kernel.org, workflows@vger.kernel.org
Subject: Re: [PATCH docs] docs: remove the tips on how to submit patches from MAINTAINERS
Date: Fri, 30 Jun 2023 15:14:48 -0700 [thread overview]
Message-ID: <4b9937d8-59b5-5a9a-df72-e7fa33728e41@infradead.org> (raw)
In-Reply-To: <20230630171550.128296-1-kuba@kernel.org>
On 6/30/23 10:15, Jakub Kicinski wrote:
> Having "how to submit patches" in MAINTAINTERS seems out of place.
> We have a whole section of documentation about it, duplication
> is harmful and a lot of the text looks really out of date.
>
> Sections 1, 2 and 4 look really, really old and not applicable
> to the modern process.
>
> Section 3 is obvious but also we have build bots now.
>
> Section 5 is a bit outdated (diff -u?!). But I like the part
> about factoring out shared code, so add that to process docs.
>
> Section 6 is unnecessary?
>
> Section 7 is covered by more appropriate docs.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> Documentation/process/6.Followthrough.rst | 7 ++
> MAINTAINERS | 80 +----------------------
> 2 files changed, 9 insertions(+), 78 deletions(-)
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
--
~Randy
next prev parent reply other threads:[~2023-06-30 22:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 17:15 Jakub Kicinski
2023-06-30 17:51 ` Jonathan Corbet
2023-06-30 18:39 ` Dan Williams
2023-06-30 18:06 ` Kees Cook
2023-06-30 22:14 ` Randy Dunlap [this message]
2023-07-03 14:35 ` 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=4b9937d8-59b5-5a9a-df72-e7fa33728e41@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=workflows@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