From: Markus Heidelberg <markus.heidelberg@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Michael Witten <mfwitten@gmail.com>,
Thomas Rast <trast@student.ethz.ch>,
Markus Heidelberg <markus.heidelberg@web.de>
Subject: [PATCH 0/6] send-email threading fixes
Date: Fri, 12 Jun 2009 12:49:26 +0200 [thread overview]
Message-ID: <1244803766-7785-1-git-send-email-markus.heidelberg@web.de> (raw)
In-Reply-To: <7vd49afjbv.fsf@alter.siamese.dyndns.org>
Junio C Hamano, 12.06.2009:
> Markus Heidelberg <markus.heidelberg@web.de> 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"
next prev parent reply other threads:[~2009-06-12 10:49 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-07 21:40 [PATCH 0/6] fixes for git-send-email Markus Heidelberg
2009-06-07 21:40 ` [PATCH 1/6] send-email: fix a typo in a comment Markus Heidelberg
2009-06-08 21:44 ` Junio C Hamano
2009-06-09 7:05 ` Markus Heidelberg
2009-06-09 7:11 ` [PATCH 1/2] add a test for git-send-email for non-threaded mails Markus Heidelberg
2009-06-09 7:11 ` [PATCH 2/2] send-email: fix " Markus Heidelberg
2009-06-07 21:40 ` [PATCH 2/6] add a test for git-send-email for threaded mails without chain-reply-to Markus Heidelberg
2009-06-07 23:28 ` Junio C Hamano
2009-06-08 5:47 ` Markus Heidelberg
2009-06-08 6:37 ` [PATCH v2 " Markus Heidelberg
2009-06-08 6:57 ` Junio C Hamano
2009-06-07 21:40 ` [PATCH 3/6] send-email: fix " Markus Heidelberg
2009-06-10 5:51 ` Junio C Hamano
2009-06-10 7:15 ` [RF sanity check] send-email threading fixes (was Re: [PATCH 3/6] send-email: fix threaded mails without chain-reply-to) Junio C Hamano
2009-06-11 16:49 ` Markus Heidelberg
2009-06-11 20:38 ` [RF sanity check] send-email threading fixes Junio C Hamano
2009-06-11 22:49 ` Markus Heidelberg
2009-06-11 23:21 ` Junio C Hamano
2009-06-12 10:49 ` Markus Heidelberg [this message]
2009-06-12 10:51 ` [PATCH 1/6] add a test for git-send-email for non-threaded mails Markus Heidelberg
2009-06-12 10:51 ` [PATCH 2/6] send-email: fix " Markus Heidelberg
2009-06-12 10:51 ` [PATCH 3/6] doc/send-email: clarify the behavior of --in-reply-to with --no-thread Markus Heidelberg
2009-06-12 10:51 ` [PATCH 4/6] add a test for git-send-email for threaded mails without chain-reply-to Markus Heidelberg
2009-06-12 10:51 ` [PATCH 5/6] send-email: fix " Markus Heidelberg
2009-06-12 10:51 ` [PATCH 6/6] send-email: fix a typo in a comment Markus Heidelberg
2009-06-10 7:16 ` [PATCH 1/6] add a test for git-send-email for non-threaded mails Junio C Hamano
2009-06-10 7:16 ` [PATCH 2/6] send-email: fix " Junio C Hamano
2009-06-10 7:16 ` [PATCH 3/6] doc/send-email: clarify the behavior of --in-reply-to with --no-thread Junio C Hamano
2009-06-10 7:17 ` [PATCH 4/6] send-email: fix threaded mails without chain-reply-to Junio C Hamano
2009-06-10 7:17 ` [PATCH 5/6] add a test for git-send-email for " Junio C Hamano
2009-06-10 7:17 ` [PATCH 6/6] send-email: fix a typo in a comment Junio C Hamano
2009-06-07 21:40 ` [PATCH 4/6] add a test for git-send-email for non-threaded mails Markus Heidelberg
2009-06-08 6:41 ` [PATCH v2 " Markus Heidelberg
2009-06-08 7:00 ` Junio C Hamano
2009-06-08 7:13 ` [PATCH v3 " Markus Heidelberg
2009-06-07 21:40 ` [PATCH 5/6] send-email: fix " Markus Heidelberg
2009-06-08 6:43 ` [PATCH v2 " Markus Heidelberg
2009-06-07 21:40 ` [PATCH 6/6] doc/send-email: clarify the behavior of --in-reply-to with --no-thread Markus Heidelberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1244803766-7785-1-git-send-email-markus.heidelberg@web.de \
--to=markus.heidelberg@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mfwitten@gmail.com \
--cc=trast@student.ethz.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).