On 28/04/2022 07:42, Bagas Sanjaya wrote: > 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? Method is the same, nothing differs. What is inaccurate in my description above around such case? Best regards, Krzysztof
