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

Re: 2 questions on git-send-email usage

From
MFmoreau francis <francis_moreau2000@yahoo.fr>
Date
Jul 11, 2006, 06:09 UTC
Message-ID
<20060711060917.34698.qmail@web25813.mail.ukl.yahoo.com>
(please let me CCed when replying)
 
 2006/7/10, Jakub Narebski <jnareb@gmail.com>:
 > moreau francis wrote:
 > 
 > > I'm wondering what am I supposed to answer when git-send-email
 > > is asking me :
 > >
 > > Message-ID to be used as In-Reply-To for the first email?
 > >
 > > I'm running this command:
 > >
 > > $ git-send-email --no-signed-off-by-cc --no-chain-reply-to --to \
 > >   foo@bar.com --compose /tmp/patch/
 > >
 > > to write an introductory message, and all patches are sent as replies to
 > > this introductory email sent.
 > 
 > Empty string (i.e. RET) should do if you don't want to attach your series of
 > patches somewhere in existing thread.
 
 ok I'll try
 
 --in-reply-to ""
 
 > 
 > > I also noticed that git-send-email removes the commit message of each
 > > patches I sent, I don't think this is the normal behaviour though. What
 > > am I missing ?
 > 
 > Are patches formatted using git-format-patch?
 > 
 
 yes
 
 Francis
Message 1 of 1 in “Re: 2 questions on git-send-email usage”
  1. moreau francisJul 11, 2006

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.