linux-kernel - Re: [PATCH v3] Documentation/process: Add text to indicate supporters should be mailed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <f7f6a67c5ee662f24885579ba09b281a5d597b0a.camel@perches.com>
Date:   Sun, 02 Oct 2022 08:49:24 -0700
From:   Joe Perches <joe@...ches.com>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        Bryan O'Donoghue <bryan.odonoghue@...aro.org>,
        Theodore Ts'o <tytso@....edu>
Cc:     Akira Yokosawa <akiyks@...il.com>, corbet@....net,
        konstantin@...uxfoundation.org, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux@...mhuis.info
Subject: Re: [PATCH v3] Documentation/process: Add text to indicate
 supporters should be mailed

On Sun, 2022-10-02 at 09:58 +0200, Krzysztof Kozlowski wrote:
> The easiest to achieve it is to run with --no-git-fallback and CC entire
> output. However it does not mean submitter must run with
> --no-git-fallback. It is only for this generic rule - CC entire output
> of get_maintainers.pl.
> 
> If you add such rule "CC entire output of get_maintainers.pl" and do not
> mention no-git-fallback, some folks will think they need to CC all these
> people who made one commit to your file...

false.

git-fallback is _not_ used when there is a listed maintainer for a
specific file.

If there is a use of git-fallback, it's because there is _no_
specified maintainer for a specific file.

   --git-fallback => use git when no exact MAINTAINERS pattern (default: 1)

i.e.: It's not "your file" if you don't maintain it.