git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Eric Sunshine <sunshine@sunshineco.com>
To: Philip Oakley <philipoakley@iee.org>
Cc: Git List <git@vger.kernel.org>
Subject: Re: How to use --cc-cmd in git-send-email?
Date: Mon, 20 Jul 2015 14:07:00 -0400	[thread overview]
Message-ID: <CAPig+cS3NxpTLJL42oV_JpxEjAJSCwrdSuJCWMQxfwK4QjEx8Q@mail.gmail.com> (raw)
In-Reply-To: <28D6CFA8D1964D34B1E7F28325AF94A8@PhilipOakley>

On Mon, Jul 20, 2015 at 10:20 AM, Philip Oakley <philipoakley@iee.org> wrote:
> From: "Eric Sunshine" <sunshine@sunshineco.com>
>> On Mon, Jul 20, 2015 at 2:01 AM, Philip Oakley <philipoakley@iee.org>
>> wrote:
>>> I may try and do a small doc patch for the git-send-email.txt man page (I
>>> have a few doc fixes backing up waiting to be done ;-)
>>
>> That would be welcome. I don't think it's mentioned at all in
>> git-send-email.txt that the --to-cmd/--cc-cmd commands are handed the
>> patch pathname as an argument, so that's certainly something worth
>> documenting.
>
> The other issue I noted was wondering what "auto-cc" is?
>
> It's only mentioned the once in:
>    --suppress-cc=<category>
>
> Specify an additional category of recipients to suppress the auto-cc of:
>
> Is it a sort of double negative? Certainly I had no idea what an auto-cc was
> ;-)

I presume that "auto-cc" refers to git-send-email's behavior of
figuring out whom to cc: automatically (by gleaning email addresses
from various sources, such as the patch itself, cc-cmd, etc.). Even
just saying "...suppress the automatic cc:'ing..." would be an
improvement, though it may deserve its own little paragraph explaining
that automatic cc:'ing is occurring and from where the email addresses
are gleaned.

      reply	other threads:[~2015-07-20 18:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-19 22:02 How to use --cc-cmd in git-send-email? Philip Oakley
2015-07-20  1:09 ` Eric Sunshine
2015-07-20  6:01   ` Philip Oakley
2015-07-20  6:06     ` Eric Sunshine
2015-07-20 14:20       ` Philip Oakley
2015-07-20 18:07         ` Eric Sunshine [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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPig+cS3NxpTLJL42oV_JpxEjAJSCwrdSuJCWMQxfwK4QjEx8Q@mail.gmail.com \
    --to=sunshine@sunshineco.com \
    --cc=git@vger.kernel.org \
    --cc=philipoakley@iee.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).