From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Linux Kernel Workflows <workflows@vger.kernel.org>
Subject: Re: maintainer profiles
Date: Mon, 13 Apr 2026 13:03:28 -0600 [thread overview]
Message-ID: <87wlyawum7.fsf@trenco.lwn.net> (raw)
In-Reply-To: <b7775383-da94-4098-8af9-2f672c4f1a71@infradead.org>
Randy Dunlap <rdunlap@infradead.org> writes:
> Hi,
>
> Is there supposed to be a difference (or distinction) in the contents of
>
> Documentation/process/maintainer-handbooks.rst
> and
> Documentation/maintainer/maintainer-entry-profile.rst
> ?
>
> Can they be combined into one location?
Late to the party, sorry ... the original idea, I believe, was that
maintainer-handbooks.rst would be for developers looking for a guidebook
for a specific subsystem, while maintainer-entry-profile.rst was about
how maintainers themselves should write their subsystem guide.
Doubtless things have drifted since then... But the intended audiences
were different, so it might be good to think about bringing them back
into focus.
jon
next prev parent reply other threads:[~2026-04-13 19:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 0:18 maintainer profiles Randy Dunlap
2026-04-10 8:12 ` Mauro Carvalho Chehab
2026-04-11 23:54 ` Randy Dunlap
2026-04-12 0:02 ` Randy Dunlap
2026-04-12 6:31 ` Mauro Carvalho Chehab
2026-04-13 19:03 ` Jonathan Corbet [this message]
2026-04-13 21:39 ` Dan Williams
2026-04-13 23:08 ` Randy Dunlap
2026-04-14 12:37 ` Mauro Carvalho Chehab
2026-04-14 14:32 ` Mauro Carvalho Chehab
2026-04-15 0:44 ` Dan Williams
2026-04-14 11:18 ` Krzysztof Kozlowski
2026-04-15 2:03 ` Randy Dunlap
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=87wlyawum7.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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