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

Re: [PATCH v3 0/2] worktree: add post-worktree lifecycle hook

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 5, 2026, 16:47 UTC
Message-ID
<xmqqwlrwjdr4.fsf@gitster.g>
In-Reply-To
<d550ede0-6a33-4eea-a6dd-051d110b68e5@mtasv.net>
The topic _claims_ to have been sent with
    X-Mailer: git-send-email 2.54.0

but it seems that the thread structure is so screwed up that some automation machinery I use seems to be having trouble locating its thread.

Here is what I see:
* Cover letter
  Subject: [PATCH v3 0/2] worktree: add post-worktree lifecycle hook
  Message-Id: <d550ede0-6a33-4eea-a6dd-051d110b68e5@mtasv.net>
  In-Reply-To: <371a01cf-2765-4cf5-b1fd-414d1b55a325@mtasv.net>
  References: <371a01cf-2765-4cf5-b1fd-414d1b55a325@mtasv.net>
* First patch
  Subject: [PATCH v3 1/2] worktree: add post-worktree lifecycle hook
  Message-Id: <2c1c1f06-05e7-4d8c-bd29-c2a9708b443d@mtasv.net>
  In-Reply-To: <cover.1791152172.git.domen@cachix.org>
  References: <371a01cf-2765-4cf5-b1fd-414d1b55a325@mtasv.net>
   <cover.1791152172.git.domen@cachix.org>
* Second patch
  Subject: [PATCH v3 2/2] worktree: notify post-worktree hook when pruning
  Message-Id: <f7ead9bc-fe6e-49c1-bb7d-6efd14eb6766@mtasv.net>
  In-Reply-To: <cover.1791152172.git.domen@cachix.org>
  References: <371a01cf-2765-4cf5-b1fd-414d1b55a325@mtasv.net>
   <cover.1791152172.git.domen@cachix.org>

Notice that the "cover letter" that are named on the In-Reply-To: header of the two patches do not match the cover letter message at all? I actually doubt the <cover.1791152172.git.domen@cachix.org> message appears anywhere in the list archive.

    ... goes and visits the URL and gets "not found" ...
    https://lore.kernel.org/git/cover.1791152172.git.domen@cachix.org/

Somebody should find out how send-email is misused to produce such a broken threading, and add some documentation to the send-email manual describing what _not_ to do, and/or update send-email code to detect such misconfiguration that caused it.

Thanks.
Previous: Domen KožarNext: Phillip Wood
Message 12 of 21 in “worktree: add post-worktree-add and post-worktree-remove hooks”
  1. 0/3 worktree: add post-worktree-add and post-worktree-remove hooksDomen Kožar, Jul 9, 2026
  2. Phillip WoodJul 10, 2026
  3. 0/4 worktree: add lifecycle hooksDomen Kožar, Aug 4, 2026
  4. Caleb WhiteAug 4, 2026
  5. Junio C HamanoAug 4, 2026
  6. Domen KožarAug 30, 2026
  7. Domen KožarSep 7, 2026
  8. Kristoffer HaugsbakkSep 7, 2026
  9. Domen KožarSep 7, 2026
  10. Maciej CiemborowiczOct 3, 2026
  11. 0/2 worktree: add post-worktree lifecycle hookDomen Kožar, Oct 4, 2026
  12. Junio C HamanoOct 5, 2026
  13. Phillip WoodJul 13, 2026
  14. 1/4 worktree: add post-worktree-add hookDomen Kožar, Aug 4, 2026
  15. Caleb WhiteAug 4, 2026
  16. 4/4 worktree: add post-worktree-move hookDomen Kožar, Aug 4, 2026
  17. 2/4 worktree: add post-worktree-remove hookDomen Kožar, Aug 4, 2026
  18. 3/4 worktree: run post-worktree-remove hook when pruningDomen Kožar, Aug 4, 2026
  19. 1/2 worktree: add post-worktree lifecycle hookDomen Kožar, Oct 4, 2026
  20. Phillip WoodOct 6, 2026
  21. 2/2 worktree: notify post-worktree hook when pruningDomen Kožar, Oct 4, 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.