{"id":103093,"date":"2022-01-25T15:36:40","date_gmt":"2022-01-25T13:36:40","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-sistemy-upravleniya-ishodnymi-tekstami-git-2-35"},"modified":"2022-01-25T15:36:40","modified_gmt":"2022-01-25T13:36:40","slug":"vypusk-sistemy-upravleniya-ishodnymi-tekstami-git-2-35","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-sistemy-upravleniya-ishodnymi-tekstami-git-2-35","title":{"rendered":"Release of the Git Source Code Management System 2.35","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
After two months of development, a release of the distributed version control system Git 2.35 has been published. Git is one of the most popular, reliable, and high-performance version control systems, offering flexible nonlinear development tools based on branching and merging. To ensure the integrity of the history and resilience to 'backdating' changes, implicit hashing of the entire previous history in each commit is used, and it is also possible to verify developers' digital signatures on individual tags and commits. <\/p>\n
Compared to the previous release, the new version includes 494 changes prepared with the participation of 93 developers, 35 of whom participated in the development for the first time. Key innovations: <\/p>\n
\n
The capabilities for using SSH keys to sign Git objects digitally have been expanded. To differentiate the validity periods of multiple keys, support for OpenSSH directives 'valid-before' and 'valid-after' has been added, which allows for proper handling of signatures after one of the developers rotates their key. Previously, there was an issue with separating signatures created with old and new keys \u2014 if the old key was deleted, it became impossible to verify signatures made with it; if kept, it would still be possible to create new signatures with the old key, even though a new key had already taken its place. With valid-before and valid-after, the scope of keys can be segmented based on the time of signature creation.\n
In the configuration setting merge.conflictStyle, which allows the selection of the conflict information display mode during a merge, support for the 'zdiff3' mode has been added. This mode moves all standard lines specified at the beginning or end of a conflict outside of the conflict area, allowing for a more compact representation of information.\n
A new mode '--staged' has been added to the 'git stash' command, which allows you to hide only the changes added to the index. This is useful in situations where you need to temporarily set aside part of complex changes to first add what is already ready, and deal with the rest later. This mode is similar to the 'git commit' command, which records only the changes placed in the index, but instead of creating a new commit, the result is saved to the temporary stash area in 'git stash --staged'. Once the changes are needed, they can be retrieved using the 'git stash pop' command.\n
A new format specifier «—format=%(describe)» has been added to the «git log» command, allowing the output of «git log» to be combined with the result of executing the «git describe» command. Parameters for «git describe» are specified directly within the specifier («—format=%(describe:match=<foo>,exclude=<bar>)»), where you can also include abbreviated tags («—format=%(describe:tags=<bool>)») and configure the number of hexadecimal characters for object identification («—format=%(describe:abbrev=<n>)»). For example, to output the last 8 commits whose tags do not have a release candidate label and specify 8-character identifiers, you can use the command: $ git log -8 —format=’%(describe:exclude=*-rc*,abbrev=13)’ v2.34.1-646-gaf4e5f569bc89 v2.34.1-644-g0330edb239c24 v2.33.1-641-g15f002812f858 v2.34.1-643-g2b95d94b056ab v2.34.1-642-gb56bd95bbc8f7 v2.34.1-203-gffb9f2980902d v2.34.1-640-gdf3c41adeb212 v2.34.1-639-g36b65715a4132\n
The user.signingKey setting now supports new key types, not limited to the «ssh-» type and the specification of a full file path to the key. Alternative types are specified using the prefix «key::», for example, «key::ecdsa-sha2-nistp256» for ECDSA keys.\n
The speed of generating the changelog in «—histogram» mode has been significantly increased, as well as when using the «—color-moved-ws» option, which controls the highlighting of spaces in colored diffs.\n
The «git jump» command, used to provide Vim with information about exact transitions to the required position in a file during merge conflict resolution, diff viewing, or search operations, has been enhanced to allow narrowing the scope of merge conflicts. For example, to restrict operations to just the «foo» directory, you can specify «git jump merge — foo», and to exclude the «Documentation» directory from processing, use «git jump merge ‘:^Documentation'».\n
Work has been done to standardize the use of the «size_t» type instead of «unsigned long» for values representing object sizes, which allows the use of «clean» and «smudge» filters with files larger than 4 GB on all platforms, including those with the LLP64 data model, in which the «unsigned long» type is limited to 4 bytes.\n
The 'git am' command has been updated with the option '--empty=(stop|drop|keep)', which allows users to choose the behavior for empty emails that do not contain patches when parsing patches from the mailbox. The value 'stop' will terminate the entire patch application operation, 'drop' will skip the empty patch, and 'keep' will create an empty commit.\n
The commands 'git reset', 'git diff', 'git blame', 'git fetch', 'git pull', and 'git ls-files' now support sparse indexes, which improve performance and save space in repositories where partial cloning (sparse-checkout) operations are performed.\n
The command 'git sparse-checkout init' is now deprecated; instead, use 'git sparse-checkout set'.\n
A preliminary implementation of the new 'reftable' backend has been added for storing references, such as branches and tags, in the repository. This new backend utilizes a block storage system developed by the JGit project and is optimized for handling a very large number of references. The backend is not yet integrated with the reference system and is not ready for practical use.\n
The color palette of the 'git grep' command has been aligned with the GNU grep utility. <\/ul>\n