The latest maintenance release Git 184.108.40.206 is available.
The release tarballs are found at:
and their SHA-1 checksums are:
Also the following public repositories all have a copy of the v220.127.116.11
tag and the maint branch that the tag points at:
url = git://repo.or.cz/alt-git.git url = https://code.google.com/p/git-core/ url = git://git.sourceforge.jp/gitroot/git-core/git.git url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core url = https://github.com/gitster/git
Git v18.104.22.168 Release Notes
Fixes since v22.214.171.124
We used to drop error messages from libcurl on certain kinds of
Error report from smart HTTP transport, when the connection was
broken in the middle of a transfer, showed a useless message on
a corrupt packet.
“git fetch –prune” was unsafe when used with refspecs from the
The attribute mechanism did not use case insensitive match when
core.ignorecase was set.
“git bisect” did not notice when it failed to update the working tree
to the next commit to be tested.
“git config –bool –get-regexp” failed to separate the variable name
and its value “true” when the variable is defined without “= true”.
“git remote rename $a $b” were not careful to match the remote name
against $a (i.e. source side of the remote nickname).
“git mergetool” did not use its arguments as pathspec, but as a path to
the file that may not even have any conflict.
“git diff –[num]stat” used to use the number of lines of context
different from the default, potentially giving different results from
“git diff | diffstat” and confusing the users.
“git pull” and “git rebase” did not work well even when GIT_WORK_TREE is
set correctly with GIT_DIR if the current directory is outside the working
“git send-email” did not honor the configured hostname when restarting
the HELO/EHLO exchange after switching TLS on.
“gitweb” used to produce a non-working link while showing the contents
Junio C Hamano wrote on 01 Nov 2011