From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation/process: use scripts/get_maintainer.pl on patches
Date: Thu, 28 Apr 2022 12:42:29 +0700 [thread overview]
Message-ID: <0d32cc45-bf65-e279-19f5-3db078ee8cc8@gmail.com> (raw)
In-Reply-To: <20220427185645.677039-1-krzysztof.kozlowski@linaro.org>
On 4/28/22 01:56, Krzysztof Kozlowski wrote:
> diff --git a/Documentation/process/3.Early-stage.rst b/Documentation/process/3.Early-stage.rst
> index 6bfd60d77d1a..894a920041c6 100644
> --- a/Documentation/process/3.Early-stage.rst
> +++ b/Documentation/process/3.Early-stage.rst
> @@ -154,10 +154,11 @@ that the kernel developers have added a script to ease the process:
> This script will return the current maintainer(s) for a given file or
> directory when given the "-f" option. If passed a patch on the
> command line, it will list the maintainers who should probably receive
> -copies of the patch. There are a number of options regulating how hard
> -get_maintainer.pl will search for maintainers; please be careful about
> -using the more aggressive options as you may end up including developers
> -who have no real interest in the code you are modifying.
> +copies of the patch. This is the preferred way (unlike "-f" option) to get the
> +list of people to Cc for your patches. There are a number of options
> +regulating how hard get_maintainer.pl will search for maintainers; please be
> +careful about using the more aggressive options as you may end up including
> +developers who have no real interest in the code you are modifying.
>
This raises my question: Supposed that I'm ready to send multiple-patch
series (two or more patches in the series). How can I get maintainers list,
given such series?
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-04-28 5:42 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 [this message]
2022-04-28 6:14 ` Krzysztof Kozlowski
2022-05-09 22:13 ` 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=0d32cc45-bf65-e279-19f5-3db078ee8cc8@gmail.com \
--to=bagasdotme@gmail.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.