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

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

From
Joe Perches <joe@perches.com>
Date
May 16, 2009, 17:15 UTC
Message-ID
<1242494103.4070.17.camel@Joe-Laptop.home>
using
  git format-patch --thread=shallow -o <foo>
and
  git send-email --no-thread --no-chain-reply-to <foo>
duplicates the headers
  In-Reply-To:
  References: 
Signed-off-by: Joe Perches <joe@perches.com>

`diff --git a/git-send-email.perl b/git-send-email.perl index cccbf45..b57bce4 100755

--- a/git-send-email.perl
+++ b/git-send-email.perl
@@ -1137,7 +1137,7 @@ foreach my $t (@files) {
 	send_message();
 
 	# set up for the next message
-	if ($chain_reply_to || !defined $reply_to || length($reply_to) == 0) {
+	if ($chain_reply_to && (!defined $reply_to || length($reply_to) == 0)) {
 		$reply_to = $message_id;
 		if (length $references > 0) {
 			$references .= "\n $message_id";
Message 1 of 1 in “git-send-email.perl: Don't add header "In-Reply-To:" when --no-chain-reply-to set”
  1. git-send-email.perl: Don't add header "In-Reply-To:" when --no-chain-reply-to setJoe Perches, May 16, 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.