All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "D. Ben Knoble" <ben.knoble@gmail.com>
Cc: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
	 Jim Cromie <jim.cromie@gmail.com>,
	 git@vger.kernel.org
Subject: Re: [PATCH 1/1] git-send-email.perl: support executable scripts for recipient options
Date: Thu, 19 Mar 2026 18:35:59 -0700	[thread overview]
Message-ID: <xmqqms03gu4g.fsf@gitster.g> (raw)
In-Reply-To: <CALnO6CAZqAacTPgwTzAyF-ryyQxaWahXmpfCt9R_+vLS0o5uAA@mail.gmail.com> (D. Ben Knoble's message of "Thu, 19 Mar 2026 12:47:58 -0400")

"D. Ben Knoble" <ben.knoble@gmail.com> writes:

>> What’s the difference between this and `--cc-cmd` and similar? I
>> wouldn’t know, I don’t use these `--*cmd` options.
>
> The only difference I can think of is that we have --cc-cmd, --to-cmd,
> but not --bcc-cmd.
>
> (I use --cc-cmd via config set to git-contacts for git.git so that
> patches mostly CC the right folks, but I typically have to manually
> track and add discussion participants, which is a bit of a pain.)

If we were inventing git-send-email today without existing users at
all, we might have appreciated the simplicity of "it is easy to tell
if the argument to --cc and other options is a name of an executable
file on disk, so do the obvious thing depending", but this came way
too late, I would have to say.

      reply	other threads:[~2026-03-20  1:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-19 15:51 [PATCH 1/1] git-send-email.perl: support executable scripts for recipient options Jim Cromie
2026-03-19 16:05 ` Kristoffer Haugsbakk
2026-03-19 16:47   ` D. Ben Knoble
2026-03-20  1:35     ` Junio C Hamano [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=xmqqms03gu4g.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=ben.knoble@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jim.cromie@gmail.com \
    --cc=kristofferhaugsbakk@fastmail.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.