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

[PATCH] Avoid composing too long "References" header.

From
YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@linux-ipv6.org>
Date
Apr 5, 2007, 23:50 UTC
Message-ID
<20070406.085024.18669509.yoshfuji@linux-ipv6.org>

The number of characters in a line MUST be no more than 998 characters, and SHOULD be no more than 78 characters (RFC2822). It is much safer to fold the header by ourselves.

Signed-off-by: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
diff --git a/git-send-email.perl b/git-send-email.perl
index ae50990..1278fcb 100755
--- a/git-send-email.perl
+++ b/git-send-email.perl
@@ -595,7 +595,7 @@ foreach my $t (@files) {
 	if ($chain_reply_to || !defined $reply_to || length($reply_to) == 0) {
 		$reply_to = $message_id;
 		if (length $references > 0) {
-			$references .= " $message_id";
+			$references .= "\n $message_id";
 		} else {
 			$references = "$message_id";
 		}
-- 
YOSHIFUJI Hideaki @ USAGI Project  <yoshfuji@linux-ipv6.org>
GPG-FP  : 9022 65EB 1ECF 3AD1 0BDF  80D8 4807 F894 E062 0EEA
Message 1 of 1 in “Avoid composing too long "References" header.”
  1. Avoid composing too long "References" header.YOSHIFUJI Hideaki / 吉藤英明, Apr 5, 2007

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.