Re: When should we release Git 3.0?

From: Michal Suchánek <msuchanek@suse.de>
Date: Oct 2, 2025, 12:13 UTC
Message-ID: <aN5sVXNdW8-GSMAE@kitsune.suse.cz>
In-Reply-To: <aN2oSBz8s_hSBMPq@fruit.crustytoothpaste.net>

On Wed, Oct 01, 2025 at 10:16:40PM +0000, brian m. carlson wrote:

Show 12 quoted lines

> On 2025-10-01 at 16:20:05, Michal Suchánek wrote:
> > From my very limited point of view as a user the interop is the major
> > planned feature currently missing in git, and I do not see much point
> > without it. Then again I do not know how useful it will be in practice.
> 
> It is the major planned feature which was missing.
> 
> The primary use cases are converting repositories and working with
> repositories using a different algorithm.  The latter might be useful if
> you're using a SHA-256 repository that someone else has created but your
> tooling cannot handle longer object IDs or otherwise has some limitation
> of that sort.

It cannot, and the compat will not help with that because it's using pygit which will not get that compat code. Presumably some baroque scheme that re-exports the repository as sha1 might be possible but it's not clear if that would be practical.

Another problem people are comlaining about is that with a mix of sha1 and sha256 repositories submodules and subtrees don't work. For that the compat might actually help but the repository will then be unintelligible to tooling that does not have compat code, which probably includes all forges at this point. Again, some baroque scheme that re-exports the repository in the other hash using the compat code might help but it's not clear if that would be practical.

Thanks

Michal