From: Joe Perches <joe@perches.com>
To: jim.cromie@gmail.com
Cc: linux-kernel@vger.kernel.org, git@vger.kernel.org
Subject: Re: [PATCH 1/1] get_maintainer.pl: add --cc option to produce comma separated list of emails
Date: Thu, 19 Mar 2026 10:08:30 -0700 [thread overview]
Message-ID: <5d28fa8fda122093fcfcf6f948f67184c0c9018e.camel@perches.com> (raw)
In-Reply-To: <CAJfuBxxbV1X3X0GdvBEEHB8gS9wQ8hHcKDGC7GrSkOPECgGV3A@mail.gmail.com>
On Thu, 2026-03-19 at 10:56 -0600, jim.cromie@gmail.com wrote:
> On Thu, Mar 19, 2026 at 10:14 AM Joe Perches <[joe@perches.com](mailto:joe@perches.com)> wrote:
> > On Thu, 2026-03-19 at 10:06 -0600, Jim Cromie wrote:
> > > This new option works as follows:
> > > git send-email --cc=$(scripts/get_maintainer.pl -cc 0*.patch) 0*.patch
> > I think this is not particularly useful.
> > Just use a script.
[1-3] remedied by script
> 4. Configuration Synergy: You can now set sendemail.cc =
> ./scripts/get_maintainer.pl in your .git/config. A shell wrapper can't
> easily override or
> augment the built-in recipient logic as cleanly as this does.
>
> That last point seems a clear win.
> Far less maintainer annoyance at not receiving the entire patchset.
That's not my experience.
This _will_ cc disinterested parties when there's a cover letter
for a large series.
prev parent reply other threads:[~2026-03-19 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 16:06 [PATCH 1/1] get_maintainer.pl: add --cc option to produce comma separated list of emails Jim Cromie
2026-03-19 16:13 ` Joe Perches
2026-03-19 16:56 ` jim.cromie
2026-03-19 17:08 ` Joe Perches [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=5d28fa8fda122093fcfcf6f948f67184c0c9018e.camel@perches.com \
--to=joe@perches.com \
--cc=git@vger.kernel.org \
--cc=jim.cromie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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