From: Eric Sunshine <sunshine@sunshineco.com>
Date: Mon, 20 Jul 2015 06:06:17 GMT
Subject: Re: How to use --cc-cmd in git-send-email?
Message-ID: <CAPig+cTsJQ+dK5M0S8LERkPWiipzxLYdbCK6-ghen1OkAX=NBg@mail.gmail.com>
In-Reply-To: <8684534127894F239338493A7D15F46D@PhilipOakley>

On Mon, Jul 20, 2015 at 2:01 AM, Philip Oakley <philipoakley@iee.org> wrote:
> From: "Eric Sunshine" <sunshine@sunshineco.com>
>> 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 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.