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

Re: [PATCH] send-email: restore --in-reply-to superseding behavior

From
Carlo Arenas <carenas@gmail.com>
Date
Jun 26, 2020, 01:08 UTC
Message-ID
<CAPUEspgoDUGUmFqoKkmKDpRzSB5dQNb+PasaPjbPwb04SBz=Ww@mail.gmail.com>
In-Reply-To
<20200625184715.GC2117795@optiplex-lnx>

a test case in t/t9001-send-email.sh will also help, as I am not sure this might be "expected behaviour" as hinted in the man page for git-send-email (under --thread):

"It is up to the user to ensure that no In-Reply-To header already exists
  exists when git send-email is asked to add it (especially note that
  git format-patch can be configured to do the threading itself).
  Failure to do so may not produce the expected result in the
  recipient's MUA."
Carlo
Previous: Rafael AquiniNext: Rafael Aquini
Message 5 of 8 in “send-email: restore --in-reply-to superseding behavior”
  1. send-email: restore --in-reply-to superseding behaviorRafael Aquini, Jun 24, 2020
  2. Junio C HamanoJun 24, 2020
  3. Rafael AquiniJun 24, 2020
  4. Rafael AquiniJun 25, 2020
  5. Carlo ArenasJun 26, 2020
  6. Rafael AquiniJun 26, 2020
  7. send-email: restore --in-reply-to superseding behaviorRafael Aquini, Jun 29, 2020
  8. Carlo Marcelo Arenas BelónJul 1, 2020

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.