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

Re: [RFC] send-email: avoid duplicate In-Reply-To and References headers

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 12, 2017, 02:51 UTC
Message-ID
<xmqq1sv4glzu.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20170212021208.GA16358@starla>
Eric Wong <e@80x24.org> writes:
Show 11 quoted lines
> Junio C Hamano <gitster@pobox.com> wrote:
>> 
>> I think it is sensibleto give priority to the --in-reply-to option
>> given from the command line over the in-file one.  I am not sure if
>> we want to drop references, though.  Wouldn't it make more sense to
>> just add what we got from the command line to what we read from the
>> file?  I dunno.
>
> You're right, existing References in the bodies should probably
> be prepended to current ones, as their order should be
> oldest-to-newest.

If you were to go that way, it may also make sense to demote the original In-Reply-To you find in the file to an entry in the References list, if it does not already appear there.

I didn't check the RFCs, but I think your original motivation is to ensure that there is not more than one messages to which the current message is replying to, iow, to ensure that there is only one message that is In-Reply-To, so appending would not be a good solution there.

Previous: Eric Wong
Message 4 of 4 in “[RFC] send-email: avoid duplicate In-Reply-To and References headers”
  1. Eric WongFeb 12, 2017
  2. Junio C HamanoFeb 12, 2017
  3. Eric WongFeb 12, 2017
  4. Junio C HamanoFeb 12, 2017

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.