{"id":182402,"date":"2026-06-30T14:48:37","date_gmt":"2026-06-30T12:48:37","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-git-2-55-c-vklyucheniem-po-umolchaniyu-podderzhki-rust"},"modified":"2026-06-30T14:48:37","modified_gmt":"2026-06-30T12:48:37","slug":"vypusk-git-2-55-c-vklyucheniem-po-umolchaniyu-podderzhki-rust","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-git-2-55-c-vklyucheniem-po-umolchaniyu-podderzhki-rust","title":{"rendered":"Git 2.55 Released with Default Rust Support","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The release of the distributed source code management system Git 2.55 has been announced. Key changes include: the default inclusion of a build with Rust, implementation of the fsmonitor process for Linux, a new strategy for repacking the incremental MIDX index, the command «git history fixup» for fixing commits, optimization of object availability bitmap generation, support for concurrent execution of hooks, and the command «git format-rev». The Git code is distributed under the GPLv2+ license.<\/p>\n
Compared to the previous release, 505 changes have been accepted in this new version, prepared with the participation of 100 developers, 33 of whom contributed to Git for the first time. Major innovations include (1, 2, 3):<\/p>\n
\n
Support for components written in Rust is enabled by default. The rustc compiler \nincluded in the list of build dependencies. To build without Rust, you can use the flag «NO_RUST=1» when running the make utility or «-Drust=disabled» during «meson configure». The option to disable the build with Rust will be supported until the Git 3.0 branch, in which Rust will become a required dependency. A layer for portability between SHA-1 and SHA-256 hash configurations has been implemented in Rust, as well as some internal functions like encoding and decoding variable-length integer values. A significant overhaul of internal Git components in Rust is expected in the future. <\/p>\n
An operation «git history fixup» for fixing commits has been added to the experimental «git history» command, which provides capabilities for rewriting change history. The «fixup» operation allows changes added through «git add» to be moved to an earlier commit, automatically rewriting all subsequent commits similar to executing the command «git commit —fixup=<commit>» and running «git rebase —autosquash <commit>~».\n
A background fsmonitor process has been implemented for the Linux platform, tracking changes in the file system using the inotify mechanism and allowing to avoid scanning the entire working directory when executing commands like «git status». Activation is managed through the «core.fsmonitor» configuration.\n
The command «git repack» has introduced the «—write-midx=incremental» mode, which implements a new strategy for updating metadata in the incremental MIDX index (multi-pack index), allowing the process to avoid repacking the entire index. In the incremental multi-pack index, instead of a single large index containing information about the distribution of objects across pack files, a layered structure is used \u2014 each layer covers a specific number of pack files and is stored in a separate bitmap file. This structure allows adding object data from new pack files to the index by attaching new layers without reconstructing the existing layers.\n
The command «git repack —write-midx=incremental» allows for adding a new layer to the incremental MIDX index that encompasses recently created pack files. Combined with the repository packing mode «—geometric», this new command enables merging new objects from multiple pack files into a larger pack file and, if necessary, packing and merging several adjacent layers of the incremental MIDX index. This strategy allows the «git repack» operation to rewrite only the top layers, leaving the older larger layers untouched, while also preventing uncontrolled growth of the layer chain, maintaining the total number of layers at a level proportional to the logarithm of the total number of objects. <\/p>\n
The generation of object availability bitmaps has been significantly optimized through a new algorithm for traversing the object tree, eliminating unnecessary recursion, caching object positions, sorting bitmaps before merging them with the XOR operation, and reworking the code for creating pseudo-merge bitmaps. In a test repository, these optimizations have reduced the bitmap generation time from 612 to 294 seconds.\n
The ability to run independent hooks in configuration files in parallel has been implemented. Hooks that affect shared state or take it into account, such as changing commit messages or inspecting indexes and the working tree, cannot be run in parallel. However, hooks for linting and unit testing can be executed simultaneously. Hooks that allow parallel execution are configured via the «hook.hook_name.parallel = true» parameter. The number of jobs that can run concurrently is determined by the hook.jobs setting, hook.<event>.jobs, or the command line option «-j».\n
The team implemented the ability to specify filters in the `git pack-objects --path-walk` command, such as `blob:none`, `blob:limit=`, `tree:0`, `object:type=`, `sparse:` and `combine:`. In the conducted test, filtering blobs while executing `--path-walk` allowed for a 16% reduction in the size of the generated pack file.\n
The `git format-rev` command has been added for formatting revisions and object names mentioned in commit lists or found in arbitrary text (for example, it can be used in hooks for processing commit messages).\n