Looking forward to Git 2.56 – and 3.0
chmaynard
76 points
30 comments
September 21, 2026
Related Discussions
Found 5 related stories in 100.0ms across 9,386 title embeddings via pgvector HNSW
- Git 3.0's upcoming SHA-256 default will be a costly mistake chmaynard · 300 pts · October 01, 2026 · 55% similar
- What Comes After Git tangled · 13 pts · September 11, 2026 · 51% similar
- What Comes After Git steveklabnik · 17 pts · September 10, 2026 · 51% similar
- We want you to build the next Git platform on Cloudflare geoffbp · 113 pts · October 03, 2026 · 49% similar
- The Git history command deserves more attention turbocon · 179 pts · July 14, 2026 · 48% similar
Discussion Highlights (5 comments)
WCSTombs
`git add --resolved` is a wonderful idea, and definitely something I would start using.
KolmogorovComp
Does it mean that when switching trop sha1 to sha256 you need to forcepush and rewrite all history? Wouldn’t that be a massive source of potential vulnerabilities?
coliveira
It is regrettable that they're trying to coerce the use of Rust everywhere just for the sake of it. It's a nonsense that is now forced on everyone.
eviks
> It is a binary file optimized for both space efficiency and quick access. Since then, it has been possible to create a repository that uses a reftable rather than the old file-based mechanism, Good, are there (m)any other plans to ditch the slow files and use proper database? Or is it only reserved for various post-git competitors?
globular-toast
Why am I not surprised that GitHub is dragging its heels on sha256? I assume they just aren't able to change fundamental parts of their system now. So no sha256, no IPv6 etc. They can only sprinkle bits around the edges.