Re: What's cooking in git.git (Jan 2025, #05; Fri, 17)

Jeff King [off-list ref] writes:

I was thinking to just leave the offending code untouched in the
individual commands if we went this route.

Ah, I see.  Yeah, then we have a subtle and possibly brittle code
paths that are well contained inside two functions.

But anyway, I'll prepare a version going the other get_be32() direction.

Thanks.  That probably results in better code with fewer magic.

THanks.