Git 2.27 neighances back: age transport protocol is standard again

Git 2.27 is backdropping: age transport protocol is standard again

The version management system git is in version 2.27 appeared and brings and brings some coquent innovations with consequences to the exhibition compatibility and a return to the previous transport protocol, which only in the transaction version 2.26 by transport protocol 2 was replaced as standard.

Backgrupation to the old transport protocol

According to release notes, the new default setting is again the process log, which until git 2.25 served as standard. Version 2 of the transport protocol presented the git team in may 2018 and in version 2.18 introduced. Apparently, the new protocol did not ran around yet, the git team has probably decided for the jerk classification.


From this version of git, the git describe command automatically outputs the long version of the code, where developers had to specify explicitly –long so far. If git describe c detects that a signed or commented day refers to the commit c and thereby eliminates the tag name t in the object, the command should now output t as an answer. This is the case, according to release notes, if developers rename the appropriate day or move from the original position in the refs / tags / hierarchy: git describe c should then continue to output t.

The git show t ^ 0 command probably does not work as usual and leads to the emptiness or may also refer to another day – depending on what is located at the item refs / tags / t. The git pull command should now output a warning message until the configuration variable pull.Rebase is defined. Who annoys or who did not want to use rebase, he had to put the variable on false to prevent this warning.

Changes in workflows and ui

Further changes concern the workflows and the user interface (ui). For example, git commit-graph write now has various options in petto to display subdivided files, and git rebase probably calls some hooks that were originally intended for checkout – but this is obviously a design error that could establish secondary (according to release notes, a documentation for this is a documentation). Numerous other changes added new functionalities and fix mistakes. The command line resistance should be mastered with the new version under command and arguments for the git worktree, and the version management system apparently offers a hand-drawn procedure for colliding names in renaming.

Around 70 developers have contributed a total of 537 commits to the new version of the open source software designed by linus torvalds 15 years ago. All changes can be found in the release notes from the mailing list. Multiple repositories offer the version management system for downloading, such as kernel googlesource and the gitster area at github.

Leave a Reply

Your email address will not be published. Required fields are marked *