{"id":105249,"date":"2022-10-04T15:36:37","date_gmt":"2022-10-04T13:36:37","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-sistemy-upravleniya-ishodnymi-tekstami-git-2-38"},"modified":"2022-10-04T15:36:37","modified_gmt":"2022-10-04T13:36:37","slug":"vypusk-sistemy-upravleniya-ishodnymi-tekstami-git-2-38","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-sistemy-upravleniya-ishodnymi-tekstami-git-2-38","title":{"rendered":"Release of Git version control system 2.38","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The release of the distributed version control system Git 2.38 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 history and resilience to 'backdated' changes, implicit hashing of the entire previous history is used in each commit, and it is also possible to verify individual tags and commits with digital signatures from developers. <\/p>\n
Compared to the previous release, this new version includes 699 changes, prepared with the participation of 92 developers, of which 24 participated in the development for the first time. Key innovations include: <\/p>\n
\n
The main component includes the 'scalar' utility, developed by Microsoft for managing large repositories. The utility was initially written in C#, but a revised version in C has been included in Git. The new utility differs from the Git command by including additional features and settings by default that affect performance when working with very large repositories. For example, when using scalar, it applies:\n
\n
Partial cloning for working with an incomplete copy of the repository.\n
A built-in change tracking mechanism for the file system (FSMonitor) that allows avoiding a scan of the entire working directory.\n
Indexes covering objects in different pack files (multi-pack).\n
Commit-graph files with a commit graph index applied to optimize access to commit information.\n
Periodic background tasks to maintain optimal repository structure in the background without blocking the interactive session (once an hour, a task is executed to preemptively load fresh objects from the remote repository and update the commit graph file, and a packing process for the repository is launched every night).\n
The 'sparseCheckoutCone' mode, which limits acceptable patterns for partial cloning. <\/ul>\n
An option '--update-refs' has been added to the 'git rebase' command to update dependent branches that intersect with moved branches, so that manual checkout operations to each dependent branch are not required to switch to the desired commit.\n
Compatibility of the 'git rm' command with partial indexes has been ensured.\n
The behavior of the 'git mv A B' command has been improved when moving a file from the working directory with partial indexes in 'cone' mode to an external area where this mode is not applied.\n
The bitmap file format has been optimized for working with large repositories\u2014an optional index table has been added with a list of selected commits and their offsets.\n
A new mode has been implemented in the 'git merge-tree' command, where a tree with the merge result is calculated based on the two specified commits, as if the histories of those commits had been combined.\n
A new setting called «safe.barerepository» has been added to manage the ability to place bare repositories (repositories that do not contain a working directory) within other git repositories. When set to «explicit», only bare repositories located in the top directory will be allowed. To enable the placement of bare repositories in subdirectories, the value «all» should be used.\n
The «git grep» command has been enhanced with the «-m» («—max-count») option, similar to the corresponding option in GNU grep, which allows limiting the number of matches displayed.\n
The «ls-files» command now includes the «—format» option for configuring the output fields (for instance, it is possible to include the display of object names, modes, etc.).\n
In «git cat-file», the display of object contents now includes the consideration of author bindings to email addresses specified in the mailmap file. <\/ul>\n