{"id":121313,"date":"2025-01-11T21:46:00","date_gmt":"2025-01-11T19:46:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-sistemy-upravleniya-ishodnymi-tekstami-git-2-48"},"modified":"2025-01-11T21:46:00","modified_gmt":"2025-01-11T19:46:00","slug":"vypusk-sistemy-upravleniya-ishodnymi-tekstami-git-2-48","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-sistemy-upravleniya-ishodnymi-tekstami-git-2-48","title":{"rendered":"Release of Git source control system 2.48","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The release of the distributed source code management system Git 2.48 has been published. Git is known for its high performance and offers tools for nonlinear development based on branching and merging branches. To ensure the integrity of history and resilience against 'backdated' changes, implicit hashing of the entire previous history in each commit is used, along with digital signatures by developers for individual tags and commits. Git's code is distributed under the GPLv2+ license. <\/p>\n
Compared to the previous release, the new version includes 605 changes prepared by 93 developers, of whom 35 are contributing for the first time. Key innovations include: <\/p>\n
\n
Support for building with the Meson build system has been implemented, in addition to GNU Make and CMake. To build Git now, you can use the command 'meson setup build && ninja -C build'. It is noted that the Makefile used with GNU Make has grown to 3887 lines and is not as simple as one would wish. The Meson toolkit simplifies working with the build system, is convenient for cross-platform builds, and makes building more accessible for newcomers or developers without experience working with Make. There are no plans to discontinue support for Make and CMake in the foreseeable future.\n
Build options have been added to allow the use of alternative SHA-1 hash implementations when computing checksums used to verify the integrity of data blocks in pack files. The performance of checksum calculations is significant; for example, about 78% of processor time is spent on their calculation when cloning a repository with the Linux kernel. The default implementation includes additional collision checks and protection against SHA-1 attacks, such as SHAttered and Shambles. Such protection, which consumes additional resources, makes sense only when using SHA-1 for cryptographic purposes and is useless when verifying the integrity of index data.\n
To build Git with a faster SHA-1 implementation that is unsuitable for cryptosystems, a series of *_UNSAFE options have been proposed, such as 'OPENSSL_SHA1_UNSAFE'. On GitHub, building with the simplified SHA-1 has allowed for a 10-13% increase in the performance of data retrieval and cloning operations. <\/p>\n
The command 'range-diff' has been enhanced with the option '--remerge-diff', allowing for the display of differences between the common merge result and the actual data reflected in the commit after executing the 'merge' command. When using the '--remerge-diff' option, the differences between conflict resolutions are not separated for each parent branch but are shown as overall differences between the file with merge conflicts and the file where the conflicts have been resolved. In the context of the 'range-diff' command, the new option can be useful for comparing sets of commits after moving the sequence of commits with the 'rebase' command using the '--rebase-merges' option.\n
The ability to run a Git test suite with memory leak detection mode has been added. Since Git provides utilities that terminate after executing the called function, memory leaks were not previously considered a significant issue. The necessity to completely eliminate memory leaks has become relevant after the work began on externalizing internal functionality into a separate library that can be applied in long-running processes.\n
The formation of a list of deprecated modes and features, the support for which is planned to be discontinued in the future, has begun. The removal of deprecated functionality is expected to occur in the Git 3.0 release, which will include changes that break backward compatibility.\n
The optimization of the team working on «git for-each-ref» has continued, producing a list of references in the repository. The optimization, which combines handlers for filtering references and formatting output, is now applied not only for unsorted output but also when using the «—sort» option.\n
The implementation of the «reftable» backend with block storage for efficient storage of references to branches and tags in the repository has been improved. Reftable significantly accelerates search, reading, and writing in repositories with a very large number of references. In the new version, some auxiliary APIs have been eliminated to further remove the libgit library from build dependencies. Adaptive error handling has been implemented, so that memory allocation errors (such as out of memory) no longer cause crashes. Link creation operations have been sped up and memory consumption reduced.\n
Issues that led to infinite loops and repository corruption after executing the «git gc» command have been resolved in the implementation of partial cloning.\n
When executing the «git fetch <remote>» command, if «refs\/remotes\/<remote>\/HEAD» is absent on the local system but a branch on the remote side that HEAD points to exists, «refs\/remotes\/<remote>\/HEAD» will now be redirected to that branch. A configuration remote.<remote>.followRemoteHEAD» has been added to manage the synchronization of «refs\/remotes\/<remote>\/HEAD» with the HEAD value on the other side.\n
A configuration «remote.<name>.serverOption» has been added, analogous to the command-line option «—serverOption=<value>».\n
In the command «git rebase —rebase-merges», the use of branch names as labels has been ensured wherever possible.\n
The ‘git notes add’ and ‘git notes append’ commands now include the ‘-e’ flag, which opens the note in an external text editor specified by the GIT_EDITOR environment variable.\n
Compatibility with GCC 15 and the C23 standard has been improved.\n
Support for older versions of libcURL and Perl has been discontinued. <\/ul>\n