From: Sylvain Rabot <sylvain@abstraction.fr>
To: git@vger.kernel.org
Subject: malformed threads when using both --in-reply-to and --compose with git send-email
Date: Tue, 30 Mar 2010 00:49:32 +0200 [thread overview]
Message-ID: <1269902972.3392.42.camel@kheops> (raw)
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
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>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2010-03-29 22:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 22:49 Sylvain Rabot [this message]
2010-03-30 14:12 ` malformed threads when using both --in-reply-to and --compose with git send-email Marc Branchaud
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1269902972.3392.42.camel@kheops \
--to=sylvain@abstraction.fr \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).