From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Mario Limonciello <mario.limonciello@amd.com>,
linux-kernel@vger.kernel.org
Cc: Joe Perches <joe@perches.com>, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 2/2] Documentation: Add a blurb about using scripts/git-send-email.sh
Date: Sun, 19 Jun 2022 10:43:47 +0700 [thread overview]
Message-ID: <10467596-9276-096f-c7c6-e0cd349eaa49@gmail.com> (raw)
In-Reply-To: <20220617183215.25917-2-mario.limonciello@amd.com>
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
prev parent reply other threads:[~2022-06-19 3:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 18:32 [PATCH 1/2] scripts: Introduce a helper script for git send-email Mario Limonciello
2022-06-17 18:32 ` [PATCH 2/2] Documentation: Add a blurb about using scripts/git-send-email.sh Mario Limonciello
2022-06-17 18:50 ` Jonathan Corbet
2022-06-17 18:54 ` Limonciello, Mario
2022-06-17 19:06 ` Joe Perches
2022-06-19 3:43 ` Bagas Sanjaya [this message]
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=10467596-9276-096f-c7c6-e0cd349eaa49@gmail.com \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome