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

question about git-send-email

From
Miklos Vajna <vmiklos@frugalware.org>
Date
Sep 26, 2007, 07:51 UTC
Message-ID
<20070926075125.GM18370@genesis.frugalware.org>
hi,

maybe i do not use git-send-email as it's expected so here is my workflow for a patch:

1) git format-patch
2) add additional comments between --- and diffstat
3) add to the patch
4) add cc the patch
5) add in-reply-to to the patch
6) invoke git send-email

2), 4) and 5) are read properly from the edited patch, but it asks again for 3). it seems it asks for the to field before it parses the mail. even worse, then it sends the mail with duplicated 'to' header if one was in the mail already.

i tried to fix it but it doesn't seem to be so trivial to me and i'm not a perl wizard :)

also i'm not sure if this usage is ok or not. just i think it's a bit confusing that 'cc' is read from the patch, but 'to'.

thanks,
- VMiklos
Message 1 of 1 in “question about git-send-email”
  1. Miklos VajnaSep 26, 2007

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.