git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 1/2] git-send-email.perl: Don't add header "In-Reply-To:" when --no-chain-reply-to set

From
Joe Perches <joe@perches.com>
Date
Jul 1, 2009, 06:27 UTC
Message-ID
<1246429653.6259.111.camel@Joe-Laptop.home>
In-Reply-To
<200907010818.57050.markus.heidelberg@web.de>
On Wed, 2009-07-01 at 08:18 +0200, Markus Heidelberg wrote:
Show 7 quoted lines
> 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.

Show 18 quoted lines
> > 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
Previous: Markus HeidelbergNext: Markus Heidelberg
Message 4 of 8 in “format-patch and send-email”
  1. 0/2 format-patch and send-emailJoe Perches, Jun 30, 2009
  2. 1/2 git-send-email.perl: Don't add header "In-Reply-To:" when --no-chain-reply-to setJoe Perches, Jun 30, 2009
  3. Markus HeidelbergJul 1, 2009
  4. Joe PerchesJul 1, 2009
  5. Markus HeidelbergJul 1, 2009
  6. Joe PerchesJul 1, 2009
  7. 2/2 format-patch: Add --cover-letter-wrapJoe Perches, Jun 30, 2009
  8. Stephen BoydJul 2, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.