workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Jakub Kicinski <kuba@kernel.org>
Cc: linux-doc@vger.kernel.org, workflows@vger.kernel.org
Subject: Re: [PATCH docs] MAINTAINERS: treat Documentation/maintainer as process docs
Date: Wed, 12 Jul 2023 10:20:32 -0600	[thread overview]
Message-ID: <87pm4x3xv3.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230712091154.7ad7561c@kernel.org>

Jakub Kicinski <kuba@kernel.org> writes:

> On Wed, 12 Jul 2023 09:10:11 -0700 Jakub Kicinski wrote:
>>  F:	Documentation/process/
>> +F:	Documentation/maintainer/
>
> Ugh, and looking at it in the email client I remember that m comes
> before p. I'll send a v2 tomorrow if nobody nacks.

See https://git.kernel.org/linus/c192ac735768 :)

jon

  reply	other threads:[~2023-07-12 16:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12 16:10 Jakub Kicinski
2023-07-12 16:11 ` Jakub Kicinski
2023-07-12 16:20   ` Jonathan Corbet [this message]
2023-07-12 16:46     ` Jakub Kicinski
2023-07-12 21:32     ` 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=87pm4x3xv3.fsf@meer.lwn.net \
    --to=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