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

Re: [PATCH 1/4] Improve message-id generation flow control for format-patch

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Feb 18, 2008, 18:00 UTC
Message-ID
<alpine.LSU.1.00.0802181759280.30505@racer.site>
In-Reply-To
<alpine.LNX.1.00.0802181229340.5816@iabervon.org>
Hi,
On Mon, 18 Feb 2008, Daniel Barkalow wrote:
> It's sort of like that, in that this *is* the caller,

Sorry, I should have been clearer. It is all too easy to forget that reasoning and use rev_info->message_id in a different way, and then mix the code paths.

Ciao, Dscho

Previous: Daniel Barkalow
Message 4 of 4 in “Improve message-id generation flow control for format-patch”
  1. 1/4 Improve message-id generation flow control for format-patchDaniel Barkalow, Feb 17, 2008
  2. Johannes SchindelinFeb 18, 2008
  3. Daniel BarkalowFeb 18, 2008
  4. Johannes SchindelinFeb 18, 2008

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.