Re: Bug in 2.48 with `git refs migrate`

From: brian m. carlson <sandals@crustytoothpaste.net>
Date: Jan 16, 2025, 23:21 UTC
Message-ID: <Z4mUizLNUdq_1BgY@tapette.crustytoothpaste.net>
In-Reply-To: <CAOLa=ZTL9n_DPhNr49XAd6bT838kc09oVx_AH7Pb4o8VK_xQ9w@mail.gmail.com>

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.

-- 
brian m. carlson (they/them or he/him)
Toronto, Ontario, CA