{"id":104517,"date":"2022-06-28T09:36:45","date_gmt":"2022-06-28T07:36:45","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-sistemy-upravleniya-ishodnymi-tekstami-git-2-37"},"modified":"2022-06-28T09:36:45","modified_gmt":"2022-06-28T07:36:45","slug":"vypusk-sistemy-upravleniya-ishodnymi-tekstami-git-2-37","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-sistemy-upravleniya-ishodnymi-tekstami-git-2-37","title":{"rendered":"Release of the Git source code management system 2.37","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The release of the distributed version control system Git 2.37 has been announced. Git is one of the most popular, reliable, and high-performance version control systems, providing flexible tools for nonlinear development based on branching and merging. To ensure the integrity of the history and resilience against 'backward changes,' implicit hashing of the entire previous history is used in each commit. Digital signatures from developers can also certify individual tags and commits. <\/p>\n
Compared to the previous release, the new version includes 395 changes prepared with the participation of 75 developers, of whom 20 contributed for the first time. Key innovations include: <\/p>\n
\n
The implementation of partial indexes (sparse index), covering only part of the repository, has been completed and is ready for widespread use. Partial indexes help boost performance and save space in repositories where sparse cloning (sparse-checkout) operations are performed or work with incomplete copies of the repository is underway. In this new release, the integration of partial indexes into the commands 'git show,' 'git sparse-checkout,' and 'git stash' has been finalized. The most noticeable performance gain from using partial indexes is observed in the 'git stash' command, where execution speed increased by up to 80% in some situations.\n
A new 'cruft packs' mechanism has been implemented for packaging unreachable objects, which are not referenced in the repository (branches or tags do not point to them). Unreachable objects are deleted by the garbage collector, but they remain in the repository for a certain period before deletion to avoid race conditions. To track the duration of unreachable objects, they need to be tagged with timestamps, which prevents their storage in the same pack file, where all objects share a common modification time. Previously, saving each object in a separate file caused issues when there were a large number of fresh unreachable objects that were not yet subject to deletion. The proposed 'cruft packs' mechanism allows all unreachable objects to be stored in a single pack file, with the modification time of each object reflected in a separate table stored in a file with the '.mtimes' extension.\n
For Windows and macOS, a built-in mechanism for tracking changes in the file system has been implemented, allowing you to avoid scanning the entire working directory when executing operations such as «git status». Previously, external file system change tracking utilities like Watchman could be connected through hooks for change tracking, but this required installing additional software and setup. Now, this functionality is built-in and can be enabled with the command «git config core.fsmonitor true».\n
The «git sparse-checkout» command has deprecated support for the alternative «--cone» mode of pattern definition for partial cloning, which allowed listing individual files using «.gitignore» syntax for the parts of the repository involved in the cloning operation, thus not allowing partial indexes to be used for optimization.\n
The flexibility of the fsync() call for flushing changes to disk has been enhanced. The «core.fsyncMethod» parameter has added support for the «batch» synchronization strategy, allowing for faster operations when writing a large number of individual files by accumulating changes in the write-back cache, flushed by a single fsync() call. A test where 500 files were added using the «git add» command completed in 0.15 seconds with the new mode enabled, while calling fsync() for each file took 1.88 seconds, and without using fsync it was 0.06 seconds.\n
In commands that traverse branches, such as «git log» and «git rev-list», a new option » —since-as-filter=X» has been added, allowing commit information older than «X» to be filtered out. Unlike the «--since» option, the new command is implemented as a filter that does not stop the iteration after the first commit older than the specified time.\n
In the «git remote» command, including the flag «-v» now provides information about partial clones of the repository.\n
A new setting, <transfer.credentialsInUrl>, has been added, which can accept the values <warn>, <die>, and <allow>. If credentials are specified in the <remote.<name>.url> parameter as plaintext, attempting to perform <fetch> or <push> operations will result in an error if the <transfer.credentialsInUrl> setting is set to <die>, or a warning if it is set to <warn>.\n
By default, a new implementation of the interactive mode for the <git add -i> command, rewritten from Perl to C, is enabled. <\/ul>\n