Gerrit attempts to set mail headers so that all messages related to a single changeset ID are threaded. Unfortunately it has screwed it up. Taking recent change " Change in openstack/nova[master]: Pin pep8 to 1.3.3", the first message has:
Message-ID: <email address hidden>
All the followup comments on that change have:
In-Reply-To: <email address hidden>
References: <email address hidden>
Notice the timestamp part of the message ID is different. The followups always have the last 3 digits as all zeros - presumably there's a precision issue with how it stores timestamps, and the first message is sent while it still has full precision ? The easy fix would seem to be to just limit the precision on the first email such that last 3 digits are always 0.
Seems this is reported upstream too
https:/