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

Re: Sending a thread of patches

From
Julian Phillips <julian@quantumfyre.co.uk>
Date
Mar 5, 2007, 02:42 UTC
Message-ID
<Pine.LNX.4.64.0703050240360.5733@beast.quantumfyre.co.uk>
In-Reply-To
<Pine.LNX.4.63.0703050324220.22628@wbgn013.biozentrum.uni-wuerzburg.de>
On Mon, 5 Mar 2007, Johannes Schindelin wrote:
Show 9 quoted lines
> Hi,
>
> On Sun, 4 Mar 2007, Julian Phillips wrote:
>
>> As far as I can figure, you don't want to use the --thread option to
>> git-format-patch when using git-send-email.
>
> That might be true. However, I consider it a bug when git-send-email does
> not replace the In-Reply-To: header, but adds a second one.
I wouldn't disagree with that.

FWIW, I seem to remember noticing that it did the same for References too ...

-- 
Julian

  ---
BOFH Excuse #323:

Your processor has processed too many instructions.  Turn it off immediately, do not type any commands!!
Previous: Johannes Schindelin
Message 5 of 5 in “Sending a thread of patches”
  1. Panagiotis IssarisMar 4, 2007
  2. Johannes SchindelinMar 4, 2007
  3. Julian PhillipsMar 4, 2007
  4. Johannes SchindelinMar 5, 2007
  5. Julian PhillipsMar 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.