After three months of development, the release of the distributed system of management of the source texts git 2.46 has been announced. GIT is one of the most popular, reliable, and high-performance version management systems that provide flexible means of nonlinear development, based on branching and merging of branches. The integrity of history and resistance to retroactive changes are ensured through implicit hashing of the entire previous story in each commit, and developers can also certify digital signatures for individual tags and commits. The GIT code is distributed under the gplv2+ license.
In the transition from the previous version to the new version, 746 changes have been implemented with the collaboration of 96 developers, 31 of whom are new to the development process. Some of the key innovations in GIT 2.46 include:
- Experimental support for a new type of bit card named “Pseudo-merge Reachability Bitmap”, a structure that stores data on sets of objects related to commits not bound to individual commits, but to multiple commits simultaneously. This new organization allows for the usage of a single bit card for determining objects for commits in different branches, eliminating the need for multiple individual bit cards and speeding up operations like Git Fetch, Git Rev-List, and Git Clone in large repositories. New settings have been introduced to configure and use this new type of bit card effectively.
- Introduction of a new command line interface for the Git Config team, which streamlines the process of viewing, renaming, and deleting settings and sections with a set of subcommands. For example, the Git Config List command can be used to display all settings in a repository, while the Git Config Get command can be used to view specific parameter contents. The addition of the “-regexp” option allows for filtering based on regular expressions.
- Enhancements in the “Credential Helper” protocol, used for transitioning to repositories with limited access by introducing support for new fields like “Authtype” and “Credential”. These additions enable the creation of handlers for HTTP authentication systems that go beyond standard login and password verification, such as using