git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: How to use --cc-cmd in git-send-email?

From
Eric Sunshine <sunshine@sunshineco.com>
Date
Jul 20, 2015, 06:06 UTC
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:
Show 18 quoted lines
> 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.

Previous: Philip OakleyNext: Philip Oakley
Message 4 of 6 in “How to use --cc-cmd in git-send-email?”
  1. Philip OakleyJul 19, 2015
  2. Eric SunshineJul 20, 2015
  3. Philip OakleyJul 20, 2015
  4. Eric SunshineJul 20, 2015
  5. Philip OakleyJul 20, 2015
  6. Eric SunshineJul 20, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.