git/list[1] front-page[2] threads[3] people[4] search[5] about
wed 2026-10-07 16:52 UTC

Re: [PATCH v6 0/3] t40*: modernize

From
Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Date
Sep 25, 2026, 13:40 UTC
Message-ID
<efec0b1a-2b02-42d3-acd9-74155925c749@gmail.com>
In-Reply-To
<DLNPWO76XNMJ.45P0NL3HVZ3H@fastmail.com>
On 9/24/26 22:50, Mark C. Chu-Carroll wrote:
Show 10 quoted lines
> On Thu Sep 24, 2026 at 10:58 AM EDT, Kaartic Sivaraam wrote:
>>
>> Just a tip, you might want to use the --in-reply-to to mention the
>> message ID of your previous iteration's cover letter. This ensures your
>> iterations end up in the same thread. With this, you do not need to
>> manually include links to the previous iteration.
> 
> Should I resend this with the in-reply-to to attach it to the thread, or
> just leave it this time?
>

I may not be the best to comment. Yet, I believe it should be fine to start doing that from the next version.

-- 
Sivaraam
Previous: Mark C. Chu-Carroll
Message 8 of 8 in “t4001: modernize”
  1. 1/3 t4001: modernizeMark C. Chu-Carroll, Sep 22, 2026
  2. 0/3 t40*: modernizeMark C. Chu-Carroll, Sep 22, 2026
  3. 2/3 t4009: modernizeMark C. Chu-Carroll, Sep 22, 2026
  4. 3/3 t4010: modernizeMark C. Chu-Carroll, Sep 22, 2026
  5. Kaartic SivaraamSep 24, 2026
  6. Junio C HamanoSep 24, 2026
  7. Mark C. Chu-CarrollSep 24, 2026
  8. Kaartic SivaraamSep 25, 2026

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.