Re: git fails to checkout SHA1 submodule in SHA256 repo with --depth=1

From: brian m. carlson <sandals@crustytoothpaste.net>
Date: Nov 15, 2025, 20:14 UTC
Message-ID: <aRjfGT_4QT4ANlVx@fruit.crustytoothpaste.net>
In-Reply-To: <b434bcb1-bf6e-4fe7-af2d-8c33348378fa@xiplink.com>

On 2025-11-14 at 22:55:07, Marc Branchaud wrote:

Show 7 quoted lines

> Set up SHA256 mirrors of the SHA1 repos you want to track in submodules?
> 
> I'm assuming that it would be easy to keep such mirrors up to date.  I'm not
> familiar enough with Brian's work to know if a SHA256 repo can have
> a SHA1 remote (which would mean that updates would just be a simple "git
> fetch origin"), but even if that's not possible I'm guessing that scripting
> some kind of regularly-run translation of new commits wouldn't be too hard.

You can set up a repository which supports both algorithms (for instance, a SHA-256 main algorithm and SHA-1 compatibility) and then interoperate with both algorithms, so yes, this is possible and it really is as easy as `git fetch origin` once set up.

The current constraint is that the cloned repository must be a full clone (not shallow or partial) and it must not have any submodules itself.

Of course, that's what the interoperability work does and it's not finished or even mostly upstreamed. As I said, it's mostly functional, but it's not production ready. It also fails many tests because we have many tests in our testsuite that require partial or shallow clones, whose support is in progress.

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