Maintainer workflows discussions
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	Linux Documentation <linux-doc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Linux Kernel Workflows <workflows@vger.kernel.org>
Subject: Re: maintainer profiles
Date: Tue, 14 Apr 2026 19:03:53 -0700	[thread overview]
Message-ID: <31369e1c-91c2-4cda-9175-c2661a7d5a82@infradead.org> (raw)
In-Reply-To: <72a4accd-5f94-45f7-8392-bb659167f078@kernel.org>



On 4/14/26 4:18 AM, Krzysztof Kozlowski wrote:
> On 10/04/2026 02:18, Randy Dunlap wrote:
>> 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?
> 
> Yes, please! Including also the location of actual profiles. I am mostly
> looking at them in the sources directly, not web docs, so confusing and
> annoying to find them distributed.

I agree completely but I'm not sure if anyone else does.

-- 
~Randy


      reply	other threads:[~2026-04-15  2:03 UTC|newest]

Thread overview: 14+ 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-15 11:43     ` Mauro Carvalho Chehab
2026-04-13 19:03 ` Jonathan Corbet
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 [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=31369e1c-91c2-4cda-9175-c2661a7d5a82@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=corbet@lwn.net \
    --cc=krzk@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@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