From: Junio C Hamano Date: Mon, 05 Oct 2026 16:47:27 GMT Subject: Re: [PATCH v3 0/2] worktree: add post-worktree lifecycle hook Message-ID: In-Reply-To: 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: 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: References: <371a01cf-2765-4cf5-b1fd-414d1b55a325@mtasv.net> * Second patch Subject: [PATCH v3 2/2] worktree: notify post-worktree hook when pruning Message-Id: In-Reply-To: References: <371a01cf-2765-4cf5-b1fd-414d1b55a325@mtasv.net> 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 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.