31
Git 3.0's upcoming SHA-256 default will be a costly mistake - gitbutler.com
(blog.gitbutler.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 03 Oct 2026
31 points (86.0% liked)
Technology
88753 readers
3504 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
Sorry for the late reply.
Again, do you have any actual evidence that SHA-256 repositories in version 3.0 won't be able to reference SHA-1 repositories as submodules?
Based on the design doc it looks like git will include both hashes during the transition, specifically to allow two-way communication with SHA-1 remotes. You may not be able to include a random stranger's SHA-1 submodule via a shallow clone, but just doing a full clone sure as heck looks like a supported usage.
https://git-scm.com/docs/hash-function-transition
I don't. If this scenario is supported, I don't see any real problem anymore.