Re: Bug in 2.48 with `git refs migrate`
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jan 17, 2025, 00:04 UTC
- Message-ID
- <xmqqmsfqnw4s.fsf@gitster.g>
- In-Reply-To
- <Z4mUizLNUdq_1BgY@tapette.crustytoothpaste.net>
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
Show 12 quoted lines
> On 2025-01-15 at 11:54:51, Karthik Nayak wrote: >> "brian m. carlson" <sandals@crustytoothpaste.net> writes: >> I'm attaching a patch below which should fixes the issue for me and also >> adding a test to test against the same. I'd be grateful if you could >> also test the patch against the repositoryies you mention. > > I can confirm that the patch did indeed fix the problem. I was able to > convert both repositories successfully (and very quickly, no less), and > they both work fine (I did normal development activity with them) with > an unmodified Git 2.48 after the migration process. > > Thanks again for the quick fix.
Thanks, both. Let's merge it down to 'next' and then to 'master', then.