linux-kernel - Re: [PATCH 2/2] Documentation: Add a blurb about using scripts/git-send-email.sh

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] [day] [month] [year] [list]

Message-ID: <10467596-9276-096f-c7c6-e0cd349eaa49@gmail.com>
Date:   Sun, 19 Jun 2022 10:43:47 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Mario Limonciello <mario.limonciello@....com>,
        linux-kernel@...r.kernel.org
Cc:     Joe Perches <joe@...ches.com>, Jonathan Corbet <corbet@....net>,
        linux-doc@...r.kernel.org
Subject: Re: [PATCH 2/2] Documentation: Add a blurb about using
 scripts/git-send-email.sh

On 6/18/22 01:32, Mario Limonciello wrote:
>  You should always copy the appropriate subsystem maintainer(s) on any patch
> -to code that they maintain; look through the MAINTAINERS file and the
> +to code that they maintain. A helper script is available in
> +./scripts/git-send-email.sh that can be used with git-send-email to automatically
> +findd the appropriate recipients for a patch.
> +Alternatively you may look through the MAINTAINERS file manually and the
>  source code revision history to see who those maintainers are.  The
>  script scripts/get_maintainer.pl can be very useful at this step (pass paths to
>  your patches as arguments to scripts/get_maintainer.pl).  If you cannot find a

s/findd/find/

Otherwise looks OK.

-- 
An old man doll... just what I always wanted! - Clara