Loading feed…
Lobsters0 Hot0 comments20 min read
Looking forward to Git 2.56 - and 3.0
Git 2.56, expected around the end of September, brings over 700 non-merge commits including an experimental git history drop subcommand, new git refs create/delete/update/rename subcommands, a --delete-merged option for git branch, and a --resolved option for git add, but no fundamental changes. The bigger story is what comes next: Git maintainer Junio Hamano asked the community whether the following release should be Git 3.0, which would bring major compatibility breaks including switching the default hash function from SHA-1 to SHA-256, adopting reftable as the default ref storage (replacing the file-based .git/refs mechanism, important for repos with hundreds of thousands of refs like Android's), rejecting uppercase object IDs, and requiring a working Rust compiler to build Git. GitHub's lack of SHA-256 support has been the main blocker, but GitHub developer brian m. carlson signaled progress is coming and favors calling the next release 3.0. libgit2 has already added reftable and default SHA-256 support, removing one obstacle. No final decision has been publicly announced yet.
Source: https://lwn.net/SubscriberLink/1094575/2385e98583715c2b. 8 Sync News only summarizes and links out; content copyright belongs to the authors and original sources.
Recommended for you
Bình luận
Đang tải bình luận…
