moreau francis <francis_moreau2000@xxxxxxxx> writes:
> Hi,
>
> Sometimes, actually most of the time, git-send-email _seems_ to not
> work properly with Thunderbird: for example if I send a patchset made
> up by 4 single patchs, then Thunderbird show me this patchset 'broken'
> that is [PATCH 2/4] is not shown as a reply to [PATCH 1/4].
> ...
> The strange thing is that all email headers are correct.
Then this is a wrong list perhaps ;-).
> I recently notice that someone has sent a patchset using
> git-send-email and I can see it 'broken' as well. The subject of the
> first email of the set is
>
> [PATCH 0/7] C cleanup series, mostly nasty shadowing
>
> Does anybody have an idea on what's going wrong ?
I see that 7+1 series as "broken"; #1 is not a reply to #0.
All others are reply to the previous one which is fine:
Subject: [PATCH 0/7] C cleanup series, mostly nasty shadowing
Message-ID: <200608231238.10963.madcoder@xxxxxxxxxx>
Subject: [PATCH 1/7] avoid to use error that shadows the funct
Message-ID: <11563295562072-git-send-email-madcoder@xxxxxxxxxx>
In-Reply-To: 200608231238.10963.madcoder@xxxxxxxxxx
Subject: [PATCH 2/7] git_dir holds pointers to local strings,
Message-ID: <11563295562422-git-send-email-madcoder@xxxxxxxxxx>
In-Reply-To: <11563295562072-git-send-email-madcoder@xxxxxxxxxx>
Subject: [PATCH 3/7] missing 'static' keywords
Message-ID: <1156329556788-git-send-email-madcoder@xxxxxxxxxx>
In-Reply-To: <11563295562422-git-send-email-madcoder@xxxxxxxxxx>
Subject: [PATCH 4/7] remove ugly shadowing of loop indexes in s
Message-ID: <11563295573215-git-send-email-madcoder@xxxxxxxxxx>
In-Reply-To: <1156329556788-git-send-email-madcoder@xxxxxxxxxx>
Subject: [PATCH 5/7] missing #define DEBUG 0 that made the prep
Message-ID: <11563295573035-git-send-email-madcoder@xxxxxxxxxx>
In-Reply-To: <11563295573215-git-send-email-madcoder@xxxxxxxxxx>
Subject: [PATCH 6/7] use name[len] in switch directly,
Message-ID: <1156329557424-git-send-email-madcoder@xxxxxxxxxx>
In-Reply-To: <11563295573035-git-send-email-madcoder@xxxxxxxxxx>
Subject: [PATCH 7/7] n is in fact unused, and is later shadowed.
Message-ID: <1156329557613-git-send-email-madcoder@xxxxxxxxxx>
In-Reply-To: <1156329557424-git-send-email-madcoder@xxxxxxxxxx>
Because #1 has a bogus In-Reply-To field, #0 and #1 would be
shown at the same level, but #2-7 would be staggered below #1.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html