All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Junio C Hamano <gitster@pobox.com>, Taylor Blau <me@ttaylorr.com>,
	Linus Arver via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org, Linus Arver <linusa@google.com>
Subject: Re: [PATCH] RFC: add MAINTAINERS file
Date: Tue, 2 Apr 2024 07:59:44 +0200	[thread overview]
Message-ID: <Zgue0LGaAa5BfqKZ@tanuki> (raw)
In-Reply-To: <CAPig+cSp=GjQWF1t+O6w+Ad=NUmeAM8ZAQp+CeetERgiSaUe0g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]

On Tue, Apr 02, 2024 at 01:46:22AM -0400, Eric Sunshine wrote:
> On Tue, Apr 2, 2024 at 1:40 AM Patrick Steinhardt <ps@pks.im> wrote:
> > When it does know about both I also see myself using it more frequently
> > in the future. It would be nice if git-send-email(1)/git-format-patch(1)
> > had a switch `--cc-command=` or similar that you can pass the script to
> > so that To/Cc lines would be added automatically. The script then gets
> > the commit range as input and can decide based on whatever criteria whom
> > to Cc. To the best of my knowledge that is not currently possible.
> 
> I may be misunderstanding your statement, but this automated mode was
> exactly the original use-case. contrib/contacts/git-contacts.txt says
> this:
> 
>     This command can be useful for determining the list of people with
>     whom to discuss proposed changes, or for finding the list of
>     recipients to Cc: when submitting a patch series via `git
>     send-email`. For the latter case, `git contacts` can be used as
>     the argument to `git send-email`'s `--cc-cmd` option.

Ah. I myself use git-format-patch(1) and mutt(1) to send the resulting
patches, and that command doesn't know about `--cc-cmd`. But
git-send-email(1) in fact does, good to know. So my statement still
partially stands, and we might want to make `--cc-cmd` available in
git-format-patch(1), too.

Patrick

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-04-02  5:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-23  3:27 [PATCH] RFC: add MAINTAINERS file Linus Arver via GitGitGadget
2024-03-23 19:19 ` Junio C Hamano
2024-03-25  2:51   ` Junio C Hamano
2024-03-27  5:33     ` Linus Arver
2024-03-27  7:17     ` Patrick Steinhardt
2024-03-30 18:03       ` Linus Arver
2024-03-30 21:44         ` Junio C Hamano
2024-04-01 21:33       ` Taylor Blau
2024-04-01 22:13         ` Junio C Hamano
2024-04-02  0:22           ` Linus Arver
2024-04-02  5:39           ` Patrick Steinhardt
2024-04-02  5:46             ` Eric Sunshine
2024-04-02  5:59               ` Patrick Steinhardt [this message]
2024-03-26 22:24   ` Linus Arver
2024-03-26 23:39   ` Taylor Blau
2024-03-27  0:05     ` Junio C Hamano
2024-03-27  4:32   ` Linus Arver
2024-03-27 13:29     ` Junio C Hamano
2024-03-30 17:59       ` Linus Arver
2024-04-02  6:22         ` Patrick Steinhardt
2024-04-04  0:47           ` Linus Arver
2024-04-02  7:00       ` Patrick Steinhardt
2024-04-02 17:00         ` Junio C Hamano

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=Zgue0LGaAa5BfqKZ@tanuki \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=gitster@pobox.com \
    --cc=linusa@google.com \
    --cc=me@ttaylorr.com \
    --cc=sunshine@sunshineco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.