public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH] Documentation/process: use scripts/get_maintainer.pl on patches
Date: Mon, 09 May 2022 16:13:24 -0600	[thread overview]
Message-ID: <87ee12cq2j.fsf@meer.lwn.net> (raw)
In-Reply-To: <20220427185645.677039-1-krzysztof.kozlowski@linaro.org>

Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> writes:

> Explain that, when collecting list of people to Cc the patch,
> scripts/get_maintainer.pl should be used on patches, not on the
> directories.  The behavior is quite different, because with "-f" on
> a directory, the maintainers of individual files will not be shown.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>
> ---
>
> It seems using the script on patches is not obvious and it already
> caused some misunderstandings.
> ---
>  Documentation/doc-guide/contributing.rst     | 5 +++--
>  Documentation/process/3.Early-stage.rst      | 9 +++++----
>  Documentation/process/submitting-patches.rst | 7 ++++---
>  3 files changed, 12 insertions(+), 9 deletions(-)

I worry about trying to cram every detail into these documents; it's not
as if their length isn't intimidating already.  But I've gone ahead and
applied this, thanks.

jon

      parent reply	other threads:[~2022-05-09 22:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 18:56 [PATCH] Documentation/process: use scripts/get_maintainer.pl on patches Krzysztof Kozlowski
2022-04-28  5:42 ` Bagas Sanjaya
2022-04-28  6:14   ` Krzysztof Kozlowski
2022-05-09 22:13 ` Jonathan Corbet [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=87ee12cq2j.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@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