The latest maintenance release Git v126.96.36.199 is now available at
the usual places.
The release tarballs are found at:
and their SHA-1 checksums are:
36180126eb2048d49b00f6092d83568df4e61c4c git-188.8.131.52.tar.gz ceb4b4699a6561719aa07e01601ed5491206c075 git-htmldocs-184.108.40.206.tar.gz 032301a87832d738149925ad2912baa554ae2270 git-manpages-220.127.116.11.tar.gz
Also the following public repositories all have a copy of the v18.104.22.168
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 v22.214.171.124 Release Notes
Fixes since v126.96.36.199
“$GIT_DIR/COMMIT_EDITMSG” file that is used to hold the commit log
message user edits was not documented.
The advise() function did not use varargs correctly to format
When “git am” failed, old timers knew to check .git/rebase-apply/patch
to see what went wrong, but we never told the users about it.
“git commit-tree” learned a more natural “-p <parent> <tree>” order
of arguments long time ago, but recently forgot it by mistake.
“git diff –no-ext-diff” did not output anything for a typechange
filepair when GIT_EXTERNAL_DIFF is in effect.
In 1.7.9 era, we taught “git rebase” about the raw timestamp format
but we did not teach the same trick to “filter-branch”, which rolled
a similar logic on its own.
When “git submodule add” clones a submodule repository, it can get
confused where to store the resulting submodule repository in the
superproject’s .git/ directory when there is a symbolic link in the
path to the current directory.
Also contains minor typofixes and documentation updates.
Changes since v188.8.131.52 are as follows:
Jeff King (3): diff: test precedence of external diff drivers advice: pass varargs to strbuf_vaddf, not strbuf_addf commit: document the temporary commit message file Jens Lehmann (1): submodules: don't stumble over symbolic links when cloning recursively Junio C Hamano (7): filter-branch: do not forget the '@' prefix to force git-timestamp date.c: Fix off by one error in object-header date parsing t7003: add test to filter a branch with a commit at epoch commit-tree: resurrect command line parsing updates Revert "git-commit-tree(1): update synopsis" diff: correctly disable external_diff with --no-ext-diff Git 184.108.40.206 Paul Gortmaker (1): am: indicate where a failed patch is to be found
Junio C Hamano wrote on 30 Jul 2012