From: "Eric Sunshine" <sunsh...@sunshineco.com>
On Mon, Jul 20, 2015 at 2:01 AM, Philip Oakley <philipoak...@iee.org>
wrote:
From: "Eric Sunshine" <sunsh...@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.
--
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 ;-)
Philip
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
