On Tue, 24 Nov 2009, Zach Welch wrote: > On Tue, 2009-11-24 at 22:08 -0500, Nicolas Pitre wrote: > > Your usage of --in-reply-to is wrong. That made all patch series to end > > up in the same thread. > > How could I have done it right? Of course, this assumes that sending 6 > patche series in reply to a top-level summary is desirable.... Anyway, > here is the relevant output from 'git send-email --help': > > --in-reply-to=<identifier> > Specify the contents of the first In-Reply-To header. Subsequent > emails will refer to the previous email instead of this if > --chain-reply-to is set (the default) Only necessary if --compose > is also set. If --compose is not set, this will be prompted for. > > It said the "first" header, darn it! I trusted the documentation! :)
It also says "... if --chain-reply-to is set" which doesn't appear to be your case despite the fact that it is said to be the default. Nicolas _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
