{"thread":{"id":"23242","subject":"malformed threads when using both --in-reply-to and --compose with git send-email","startedAt":"2010-03-29T22:49:32Z","lastAt":"2010-03-30T14:12:57Z","messageCount":2,"participants":["Sylvain Rabot","Marc Branchaud"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"138139","messageId":"1269902972.3392.42.camel@kheops","threadId":"23242","inReplyTo":null,"subject":"malformed threads when using both --in-reply-to and --compose with git send-email","fromName":"Sylvain Rabot","fromEmail":"sylvain@abstraction.fr","sentAt":"2010-03-29T22:49:32Z","receivedAt":"2010-03-29T22:49:32Z","isPatch":false,"sender":{"key":"sylvain@abstraction.fr","avatar":"https://avatars.githubusercontent.com/u/153052?v=4"},"body":"Hey,\n\nI don't know if it's the wanted behavior but It seemed odd to me.\n\nIf I want to send a series of patches to an already started thread using\n--in-reply-to option and --compose this is what I would get :\n\ngit send-email --to git@vger.kernel.org --compose --in-reply-to <Message\n#2> --format-patch HEAD~2\n\n+ Message #1\n  + Message #2\n    + [PATCH 0/2] My Serie of patches\n    + [PATCH 1/2] My first patch\n    + [PATCH 2/2] My second patch\n\nI would have expected something more like this which is done when\nstarting a new thread :\n\n+ Message #1\n  + Message #2\n    + [PATCH 0/2] My Serie of patcher (In-Reply-To : <Message #2>)\n      + [PATCH 1/2] My first patch (In-Reply-To : <My Serie of patches>)\n      + [PATCH 2/2] My second patch (In-Reply-To : <My Serie of\npatches>)\n\nRegards.\n\n-- \nSylvain Rabot <sylvain@abstraction.fr>\n"},{"id":"138181","messageId":"4BB206E9.8050807@xiplink.com","threadId":"23242","inReplyTo":"1269902972.3392.42.camel@kheops","subject":"Re: malformed threads when using both --in-reply-to and --compose with git send-email","fromName":"Marc Branchaud","fromEmail":"marcnarc@xiplink.com","sentAt":"2010-03-30T14:12:57Z","receivedAt":"2010-03-30T14:12:57Z","isPatch":false,"sender":{"key":"marcnarc@xiplink.com","avatar":"https://avatars.githubusercontent.com/u/14980203?v=4"},"body":"Sylvain Rabot wrote:\n> Hey,\n> \n> I don't know if it's the wanted behavior but It seemed odd to me.\n> \n> If I want to send a series of patches to an already started thread using\n> --in-reply-to option and --compose this is what I would get :\n> \n> git send-email --to git@vger.kernel.org --compose --in-reply-to <Message\n> #2> --format-patch HEAD~2\n> \n> + Message #1\n>   + Message #2\n>     + [PATCH 0/2] My Serie of patches\n>     + [PATCH 1/2] My first patch\n>     + [PATCH 2/2] My second patch\n> \n> I would have expected something more like this which is done when\n> starting a new thread :\n> \n> + Message #1\n>   + Message #2\n>     + [PATCH 0/2] My Serie of patcher (In-Reply-To : <Message #2>)\n>       + [PATCH 1/2] My first patch (In-Reply-To : <My Serie of patches>)\n>       + [PATCH 2/2] My second patch (In-Reply-To : <My Serie of\n> patches>)\n\nI encountered this as well and agree with you that the latter would be\nbetter.  --compose should only apply the --in-reply-to value to the composed\nmessage.\n\nCare to make a patch?\n\n\t\tM.\n"}]}