From: "Philip Oakley" <philipoakley@iee.org>
To: "Eric Sunshine" <sunshine@sunshineco.com>
Cc: "Git List" <git@vger.kernel.org>
Subject: Re: How to use --cc-cmd in git-send-email?
Date: Mon, 20 Jul 2015 07:01:44 +0100 [thread overview]
Message-ID: <8684534127894F239338493A7D15F46D@PhilipOakley> (raw)
In-Reply-To: CAPig+cTQspD+0StY5tneqwekS3xCjdxcidoDA7Ztf26g-tMucg@mail.gmail.com
From: "Eric Sunshine" <sunshine@sunshineco.com>
> On Sun, Jul 19, 2015 at 6:02 PM, Philip Oakley <philipoakley@iee.org>
> wrote:
>> I've been using git-send-email with repeated individual --cc="email
>> address"
>> parameters on the command line.
>>
>> I tried putting all the addresses, one per line, into a file
>> 'cc-cmd', so I
>> could use if for the --cc-cmd option.
>>
>> I then tried to use --cc-cmd='cat cc-cmd' to do the send-email (as a
>> --dry-run). This produced, as part of the output, a list of the
>> output of
>> the cc-cmd, which showed not only the file contents, but this was
>> then
>> followed by the full patch, as if it was part of the list of email
>> addresses.
>
> git-send-email invokes the cc-cmd like this:
>
> $cc-cmd $patchfilename
>
> so, when you used 'cat cc-cmd' as the value of --cc-cmd, your
> invocation became:
>
> cat cc-cmd $patchfilename
>
> and since 'cat' copies the concatenation of its input files to its
> output, that explains why you first saw the names from your 'cc-cmd'
> file followed by the content of the patch file.
Many thanks, that seems to explain everything!
I'd tried to understand the code but I missed the nuances with my
limited experience of perl coding.
>
> A quick-and-dirty work-around is to use '#' to effectively comment out
> the patch file name:
>
> --cc-cmd='cat cc-cmd #'
>
> which works, but is very, very ugly.
But nicely quick and dirty ;-)
>
>> Could this have been caused by an extra (blank) line at the end of
>> the
>> cc-cmd file?
>
> Nope.
>
>> Also, does anyone have an example of a working --cc-cmd option?
>
> A very simple working solution is to make your 'cc-cmd' file
> executable:
>
> #!/bin/sh
> echo <<\EOF
> person1@example.com
> person2@example.com
> EOF
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 ;-)
--
Philip
next prev parent reply other threads:[~2015-07-20 6:05 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 [this message]
2015-07-20 6:06 ` Eric Sunshine
2015-07-20 14:20 ` Philip Oakley
2015-07-20 18:07 ` Eric Sunshine
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=8684534127894F239338493A7D15F46D@PhilipOakley \
--to=philipoakley@iee.org \
--cc=git@vger.kernel.org \
--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.
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).