Hello Ulf, On Tue, Dec 30, 2014 at 11:29 AM, Ulf Hansson <ulf.hansson@xxxxxxxxxx> wrote: > On 19 December 2014 at 20:02, Doug Anderson <dianders@xxxxxxxxxxxx> wrote: >> >>> It was a bit hard to follow the >>> updated the revisions, please don't send patches "in-reply-to" for >>> future sets. >> >> Very strange. I didn't send out anything in-reply-to other than what >> git-send-email usually does. I believe I had: >> >> [0] - no in reply to. >> [1] - in reply to [0] >> [2] - in reply to [0] >> [3] - in reply to [0] >> [4] - in reply to [0] > > That's good. As long as there are no in-reply to previous versions of > patches/patchsets. > > I am using gmails web-based client so it could very well be that it > does some magic, which I am not yet aware of. > I think that you were confused because Gmail's "conversation view" groups emails in a thread not by the email subject but by the email body. So if a new revision of a series is sent and a patch did not change from the previous version, Gmail will add it to the old patch thread since the body is basically the same even when a version is present in the subject (e.g: PATCH v2 foo). I found that annoying as well so I disabled conversation view going to Gmail's settings -> General -> Conversation view off Hope it helps. Best regards, Javier -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
