Jacob Keller <jacob.e.keller@xxxxxxxxx> writes:
>>> 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.
