From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Antonio Ospite <ospite@studenti.unina.it>
Cc: git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>,
"Jonathan Nieder" <jrnieder@gmail.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Brandon Casey" <drafnel@gmail.com>,
"Stephen Boyd" <bebarino@gmail.com>,
"Thomas Rast" <trast@student.ethz.ch>
Subject: Re: [PATCH v3] git-send-email.perl: make initial In-Reply-To apply only to first email
Date: Fri, 05 Nov 2010 23:36:02 +0100 [thread overview]
Message-ID: <vpqtyjvo0tp.fsf@bauges.imag.fr> (raw)
In-Reply-To: <1288990769-13307-1-git-send-email-ospite@studenti.unina.it> (Antonio Ospite's message of "Fri\, 5 Nov 2010 21\:59\:29 +0100")
Antonio Ospite <ospite@studenti.unina.it> writes:
> When an initial In-Reply-To is supplied it should apply only to the
> first email, second and subsequent messages should behave just according
> to the --[no-]chain-reply-to setting; this is the typical behaviour we
> want when we send a series with cover letter in reply to some
> discussion,
+1 on this. I've been biten by this behavior sending the v2 of
a patch serie --in-reply-to the cover letter for the v1. The two
versions of each patch appear as reply to the original cover letter,
it's kind of a mess. I was really expecting the patch serie to appear
as a separate subtree in the discussion.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2010-11-05 22:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 9:38 [PATCH] git-send-email.perl: fix In-Reply-To for second and subsequent patches Antonio Ospite
2010-10-14 18:22 ` Jonathan Nieder
2010-10-15 7:56 ` Antonio Ospite
2010-10-19 9:52 ` [PATCH v2] " Antonio Ospite
2010-10-19 18:26 ` Junio C Hamano
2010-10-19 18:45 ` Junio C Hamano
2010-10-19 22:45 ` Antonio Ospite
2010-10-26 13:50 ` Antonio Ospite
2010-11-05 20:59 ` [PATCH v3] git-send-email.perl: make initial In-Reply-To apply only to first email Antonio Ospite
2010-11-05 22:36 ` Matthieu Moy [this message]
2010-11-09 21:23 ` Junio C Hamano
2010-11-10 11:45 ` Antonio Ospite
2010-11-10 19:48 ` Junio C Hamano
2010-11-12 14:55 ` [PATCHi v4] " Antonio Ospite
2010-11-12 20:53 ` Junio C Hamano
2010-11-12 21:44 ` Junio C Hamano
2010-11-12 22:51 ` Antonio Ospite
2010-11-05 21:41 ` [PATCH v2] git-send-email.perl: fix In-Reply-To for second and subsequent patches Jonathan Nieder
2010-11-08 11:03 ` Antonio Ospite
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=vpqtyjvo0tp.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=avarab@gmail.com \
--cc=bebarino@gmail.com \
--cc=drafnel@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=ospite@studenti.unina.it \
--cc=trast@student.ethz.ch \
/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).