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

Re: [PATCH] send-email: avoid duplicate In-Reply-To/References

From
EWEric Wong <e@80x24.org>
Date
Apr 18, 2018, 00:54 UTC
Message-ID
<20180418005415.GA31588@dcvr>
In-Reply-To
<20180417211630.22873-1-stefan@agner.ch>
Stefan Agner <stefan@agner.ch> wrote:
> This addresses the issue reported here:
> https://public-inbox.org/git/997160314bbafb3088a401f1c09ccb08@agner.ch/
Thanks for bringing this up.
Show 12 quoted lines
> --- a/git-send-email.perl
> +++ b/git-send-email.perl
> @@ -1642,10 +1642,15 @@ foreach my $t (@files) {
>  			elsif (/^Content-Transfer-Encoding: (.*)/i) {
>  				$xfer_encoding = $1 if not defined $xfer_encoding;
>  			}
> +			elsif (/^In-Reply-To: (.*)/i) {
> +				$in_reply_to = $1;
> +			}
> +			elsif (/^References: (.*)/i) {
> +				$references = $1;
> +			}
References: can span multiple lines with --thread=deep in format-patch
(technically any header can be, but References: is common)
Previous: Stefan AgnerNext: Stefan Agner
Message 2 of 3 in “send-email: avoid duplicate In-Reply-To/References”
  1. send-email: avoid duplicate In-Reply-To/ReferencesStefan Agner, Apr 17, 2018
  2. Eric WongApr 18, 2018
  3. Stefan AgnerApr 18, 2018

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.