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

malformed threads when using both --in-reply-to and --compose with git send-email

From
Sylvain Rabot <sylvain@abstraction.fr>
Date
Mar 29, 2010, 22:49 UTC
Message-ID
<1269902972.3392.42.camel@kheops>
Hey,
I don't know if it's the wanted behavior but It seemed odd to me.

If I want to send a series of patches to an already started thread using --in-reply-to option and --compose this is what I would get :

git send-email --to git@vger.kernel.org --compose --in-reply-to <Message #2> --format-patch HEAD~2

+ Message #1
  + Message #2
    + [PATCH 0/2] My Serie of patches
    + [PATCH 1/2] My first patch
    + [PATCH 2/2] My second patch

I would have expected something more like this which is done when starting a new thread :

+ Message #1
  + Message #2
    + [PATCH 0/2] My Serie of patcher (In-Reply-To : <Message #2>)
      + [PATCH 1/2] My first patch (In-Reply-To : <My Serie of patches>)
      + [PATCH 2/2] My second patch (In-Reply-To : <My Serie of
patches>)
Regards.
-- 
Sylvain Rabot <sylvain@abstraction.fr>
Next: Marc Branchaud
Message 1 of 2 in “malformed threads when using both --in-reply-to and --compose with git send-email”
  1. Sylvain RabotMar 29, 2010
  2. Marc BranchaudMar 30, 2010

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.