All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Domen Kožar" <domen@cachix.org>
Cc: git@vger.kernel.org,  cdwhite3@pm.me,  phillip.wood123@gmail.com,
	sunshine@sunshineco.com,  ps@pks.im,  avarab@gmail.com,
	test35965@gmail.com,  kristofferhaugsbakk@fastmail.com,
	maciej.ciemborowicz@gmail.com
Subject: Re: [PATCH v3 0/2] worktree: add post-worktree lifecycle hook
Date: Mon, 05 Oct 2026 09:47:27 -0700	[thread overview]
Message-ID: <xmqqwlrwjdr4.fsf@gitster.g> (raw)
In-Reply-To: <d550ede0-6a33-4eea-a6dd-051d110b68e5@mtasv.net> ("Domen Kožar"'s message of "Sun, 04 Oct 2026 23:09:07 +0000")

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.

  reply	other threads:[~2026-10-05 16:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09 23:36 [PATCH v1 0/3] worktree: add post-worktree-add and post-worktree-remove hooks Domen Kožar
2026-07-10  9:34 ` Phillip Wood
     [not found]   ` <CAMvcdZS=ZYbLmjKaGJvjQ_fWYhVbOzwMvYq+MMENWPYi_RiqvQ@mail.gmail.com>
2026-07-13 13:19     ` Phillip Wood
2026-08-04 18:14 ` [PATCH v2 0/4] worktree: add lifecycle hooks Domen Kožar
2026-08-04 19:03   ` Caleb White
2026-08-04 20:28     ` Junio C Hamano
2026-08-30 17:21       ` Domen Kožar
2026-09-07 14:30         ` Domen Kožar
2026-09-07 18:18           ` Kristoffer Haugsbakk
2026-09-07 19:34             ` Domen Kožar
2026-10-03 18:47       ` Maciej Ciemborowicz
2026-10-04 23:09   ` [PATCH v3 0/2] worktree: add post-worktree lifecycle hook Domen Kožar
2026-10-05 16:47     ` Junio C Hamano [this message]
     [not found]   ` <cover.1791152172.git.domen@cachix.org>
2026-10-04 23:09     ` [PATCH v3 1/2] " Domen Kožar
2026-10-06  9:23       ` Phillip Wood
2026-10-04 23:09     ` [PATCH v3 2/2] worktree: notify post-worktree hook when pruning Domen Kožar
     [not found] ` <20260804181358.532970-1-domen@cachix.org>
2026-08-04 18:14   ` [PATCH v2 1/4] worktree: add post-worktree-add hook Domen Kožar
2026-08-04 20:03     ` Caleb White
2026-08-04 18:14   ` [PATCH v2 2/4] worktree: add post-worktree-remove hook Domen Kožar
2026-08-04 18:14   ` [PATCH v2 3/4] worktree: run post-worktree-remove hook when pruning Domen Kožar
2026-08-04 18:14   ` [PATCH v2 4/4] worktree: add post-worktree-move hook Domen Kožar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqwlrwjdr4.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=cdwhite3@pm.me \
    --cc=domen@cachix.org \
    --cc=git@vger.kernel.org \
    --cc=kristofferhaugsbakk@fastmail.com \
    --cc=maciej.ciemborowicz@gmail.com \
    --cc=phillip.wood123@gmail.com \
    --cc=ps@pks.im \
    --cc=sunshine@sunshineco.com \
    --cc=test35965@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.