Alex, On Mon, Oct 17, 2011 at 04:04:21PM -0500, Austin, Alex wrote: > > -----Original Message----- > > From: openocd-development-boun...@lists.berlios.de [mailto:openocd- > > development-boun...@lists.berlios.de] On Behalf Of Jason > > > > ... > > > > 1.) Threading versions of a patch series together. So, when the > > maintainer has a chance to look at the thread, he/she can just go to the > > end of the thread to get the latest version. This would require a > > hook script in 'git format-patch' to add In-Reply-To: and to do patch > > versioning (read and detect from output directory?). Possibly, > > --versioning? Basically, I'm replacing gerrit's "Change-Id" with smtp's > > already useful "Message-Id" and "In-Reply-To". > > Could the Message-Id be set to, exactly, the Change-Id?
I'd have to check the RFC [1], but technically, they are both globally unique identifiers. So, I don't see why not. gerrit would have to be modified to look for a Change-Id in the headers of the email, and accept that the first version of a patch series already has a Change-Id assigned. Nothing impossible, there. >From a quick glance at the RFC, the Message-Id is required to be globally unique, and _common_practice_ is to use epoch time in seconds '@hostname.tld'. If we're modding gerrit, we could probably do: Message-Id: <gerrit-change-id-id_is_h...@users.mailserver.tld> and have gerrit parse it out. That would align with common practice and be readily parsible. thx, Jason. [1] http://tools.ietf.org/html/rfc2392 _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
