From: Markus Heidelberg Date: Fri, 12 Jun 2009 10:49:26 GMT Subject: [PATCH 0/6] send-email threading fixes Message-ID: <1244803766-7785-1-git-send-email-markus.heidelberg@web.de> In-Reply-To: <7vd49afjbv.fsf@alter.siamese.dyndns.org> Junio C Hamano, 12.06.2009: > Markus Heidelberg writes: > > > HTH and I got everything explained correctly. > > Now, you can summarize the series with a proper [0/6], perhaps modelling > after how I explained the order of application and merge structure ;-). OK, I'll try :) For easier understanding I kept the wording from your reshuffled series. [PATCH 1/6] add a test for git-send-email for non-threaded mails [PATCH 2/6] send-email: fix non-threaded mails [PATCH 3/6] doc/send-email: clarify the behavior of --in-reply-to with --no-thread [PATCH 4/6] add a test for git-send-email for threaded mails without chain-reply-to [PATCH 5/6] send-email: fix threaded mails without chain-reply-to [PATCH 6/6] send-email: fix a typo in a comment The first three patches apply to the tip of 'maint', which is currently at 94af7c3 (Documentation: git-send-mail can take rev-list arg to drive format-patch, 2009-06-11). The first one exposes breakage introduced by 3e0c4ff and then the second one fixes it. The last three patches apply to the tip of 'master'. Patch 4/6 exposes breakage introduced by 15da108, patch 5/6 fixes it. Changes compared to 'pu': * adjusted the description of 2/6 to hopefully add less confusion * changed the order of 4/6 and 5/6 and applied 5/6 directly on top of 4/6, since the regression was immediately noticable * also change test_expect_failure to test_expect_success in 5/6 then * instead of in the former merge commit a6f8abc "Merge branch 'mh/master-send-email-threaded-fix' into mh/master-send-email"