From: Joe Perches <joe@perches.com>
To: markus.heidelberg@web.de
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] git-send-email.perl: Don't add header "In-Reply-To:" when --no-chain-reply-to set
Date: Tue, 30 Jun 2009 23:27:33 -0700 [thread overview]
Message-ID: <1246429653.6259.111.camel@Joe-Laptop.home> (raw)
In-Reply-To: <200907010818.57050.markus.heidelberg@web.de>
On Wed, 2009-07-01 at 08:18 +0200, Markus Heidelberg wrote:
> Joe Perches, 01.07.2009:
> > using
> > git format-patch --thread=shallow -o <foo>
> > and
> > git send-email --no-thread --no-chain-reply-to <foo>
>
> I guess you meant --thread here.
Actually, I did mean --no-thread.
If format-patch does the threading, send-email shouldn't.
> > duplicates the headers
> >
> > In-Reply-To:
> > References:
>
> You should run at least the test from the test suite for the particular
> command you change. Test 49 (threading but no chain-reply-to) from t9001
> now fails.
>
> That means, this will fail now (covered by test 49):
>
> git format-patch -o <foo>
> git send-email --thread --no-chain-reply-to <foo>
>
> and also this (not covered by any test, maybe we should add one):
>
> git format-patch -o <foo>
> git send-email --thread --chain-reply-to <foo>
I didn't know the tests existed, thanks.
I'll investigate a bit more.
cheers, Joe
next prev parent reply other threads:[~2009-07-01 6:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 23:40 [PATCH 0/2] format-patch and send-email Joe Perches
2009-06-30 23:40 ` [PATCH 1/2] git-send-email.perl: Don't add header "In-Reply-To:" when --no-chain-reply-to set Joe Perches
2009-07-01 6:18 ` Markus Heidelberg
2009-07-01 6:27 ` Joe Perches [this message]
2009-07-01 16:59 ` Markus Heidelberg
2009-07-01 17:25 ` Joe Perches
2009-06-30 23:40 ` [PATCH 2/2] format-patch: Add --cover-letter-wrap Joe Perches
2009-07-02 6:45 ` Stephen Boyd
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1246429653.6259.111.camel@Joe-Laptop.home \
--to=joe@perches.com \
--cc=git@vger.kernel.org \
--cc=markus.heidelberg@web.de \
/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.
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 NNTP newsgroup(s).