Re: [RFC PATCH 0/2] fetch --prune performance problem
- From
Jacob Keller <jacob.e.keller@intel.com>
- Date
- Jun 23, 2025, 23:46 UTC
- Message-ID
- <628070ea-8fde-4a67-a05d-8d88858cde95@intel.com>
- In-Reply-To
- <CABURp0q-1FGmD+PJeSQ=xvyDN6ZYn1O7Fh8i1OojfD2WQCqgcw@mail.gmail.com>
On 6/23/2025 4:40 PM, Phil Hord wrote:
Show 25 quoted lines
> On Mon, Jun 23, 2025 at 4:32 PM Jacob Keller <jacob.e.keller@intel.com> >> On 6/23/2025 4:11 PM, Phil Hord wrote: >>> 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. > > That's because I used the `--dry-run` switch. Sorry for the confusion. > > + git fetch --prune > From /tmp/repo/. > - [deleted] (none) -> origin/branches > - [deleted] (none) -> origin/master > - [deleted] (none) -> origin/other > origin/HEAD has become dangling after origin/master was deleted >
Aha! That is even better that it properly adjusts the text based on --dry-run.
I like it.
Regards, Jake