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 for Android: free password hash cracker in your pocket

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

Message-ID: <dabbb4aa-d5e1-10d5-082c-1386f3314fc8@linaro.org>
Date:   Sun, 2 Oct 2022 09:58:25 +0200
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     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 01/10/2022 12:37, Bryan O'Donoghue wrote:
> 
> I wasn't sure how people would necessarily feel about having 
> get_maintainer produce the string 'maintainer' for both Maintained and 
> Supported but, IMO it is more consistent to have it do so, since we 
> refer to maintainers all throughout the doucmentation and as you say 
> above Rafael is the person you *need* to mail there because he's the 
> maintainer.
> 
> Lets consider
> 
> - maintainer as a string for "S: Supported"
> - Documentation update to reflect Krzysztof's point on git-fallback

Just to clarify my point - one can use git-fallback. The expectation is
however that submitter CCs all specifically assigned addresses from
maintainers, this is:
 - all maintainers
 - all maintainers-supporters
 - all reviewers
 - all dedicated mailing lists
 - LKML if there is no dedicated mailing list.

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...

Best regards,
Krzysztof