From: "brian m. carlson" <sandals@crustytoothpaste•net>
To: Marc Branchaud <marcnarc@xiplink•com>
Cc: Martin Wilck <mwilck@suse•com>,
Junio C Hamano <gitster@pobox•com>,
git@vger•kernel.org, Adrian Schroeter <adrian@suse•com>
Subject: Re: git fails to checkout SHA1 submodule in SHA256 repo with --depth=1
Date: Sat, 15 Nov 2025 20:14:17 +0000 [thread overview]
Message-ID: <aRjfGT_4QT4ANlVx@fruit.crustytoothpaste.net> (raw)
In-Reply-To: <b434bcb1-bf6e-4fe7-af2d-8c33348378fa@xiplink.com>
[-- Attachment #1: Type: text/plain, Size: 1296 bytes --]
On 2025-11-14 at 22:55:07, Marc Branchaud wrote:
> 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2025-11-15 20:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 12:58 git fails to checkout SHA1 submodule in SHA256 repo with --depth=1 Martin Wilck
2025-11-12 16:32 ` Junio C Hamano
2025-11-12 23:37 ` brian m. carlson
2025-11-13 10:15 ` Martin Wilck
2025-11-13 22:51 ` brian m. carlson
2025-11-13 22:57 ` Martin Wilck
2025-11-14 22:55 ` Marc Branchaud
2025-11-15 20:14 ` brian m. carlson [this message]
2025-11-12 23:54 ` [PATCH] object-file: disallow adding submodules of different hash algo brian m. carlson
2025-11-13 3:26 ` Jeff King
2025-11-13 3:56 ` Jeff King
2025-11-13 16:29 ` Junio C Hamano
2025-11-14 23:26 ` brian m. carlson
2025-11-15 1:53 ` Jeff King
2025-11-13 23:15 ` brian m. carlson
2025-11-15 0:58 ` [PATCH v2 1/2] " brian m. carlson
2025-11-15 0:58 ` [PATCH v2 2/2] read-cache: drop submodule check from add_to_cache() brian m. carlson
2025-11-15 19:57 ` Junio C Hamano
2025-11-15 20:06 ` brian m. carlson
2025-11-15 19:53 ` [PATCH v2 1/2] object-file: disallow adding submodules of different hash algo Junio C Hamano
2025-11-17 8:53 ` Martin Wilck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aRjfGT_4QT4ANlVx@fruit.crustytoothpaste.net \
--to=sandals@crustytoothpaste$(echo .)net \
--cc=adrian@suse$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=marcnarc@xiplink$(echo .)com \
--cc=mwilck@suse$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox