Re: [RFC PATCH 0/2] fetch --prune performance problem

From: Junio C Hamano <gitster@pobox.com>
Date: Jun 23, 2025, 23:41 UTC
Message-ID: <xmqq4iw63u1i.fsf@gitster.g>
In-Reply-To: <f11bf463-0005-43d2-b642-ede130d1f44c@intel.com>

Jacob Keller <jacob.e.keller@intel.com> writes:

Show 21 quoted lines

>>> Alternatively, the dangling message could just mention where it the
>>> now-dangling symref points at, something like:
>>>
>>>    - [deleted]         (none)     -> origin/branches
>>>    - [deleted]         (none)     -> origin/main
>>>    - [deleted]         (none)     -> origin/other
>>>      (refs/remotes/origin/HEAD points to the now-deleted origin/main)
>> 
>> I have a new patch that produces this:
>> 
>>     + git fetch --prune --dry-run
>>     From /tmp/repo/.
>>      - [deleted]                   (none)     -> origin/branches
>>      - [deleted]                   (none)     -> origin/master
>>      - [deleted]                   (none)     -> origin/other
>>        origin/HEAD will become dangling after origin/master is deleted
>> 
>
>
> It is a bit weird that this says "will become dangling after <ref> is
> deleted" because the deletion already happened.

But that is with "--dry-run".  Without it, presumably

    origin/HEAD is now dangling since origin/master was deleted

or something, probably.