-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
- -------- Forwarded Message -------- Subject: [ANNOUNCE] Git v2.1.1 Date: Fri, 19 Sep 2014 15:53:45 -0700 From: Junio C Hamano <[email protected]> To: [email protected] CC: Linux Kernel <[email protected]> The latest maintenance release Git v2.1.1 is now available at the usual places. The tarballs are found at: https://www.kernel.org/pub/software/scm/git/ The following public repositories all have a copy of the 'v2.1.1' tag and the 'maint' branch that the tag points at: url = https://kernel.googlesource.com/pub/scm/git/git 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 v2.1.1 Release Notes ======================== * Git 2.0 had a regression where "git fetch" into a shallowly cloned repository from a repository with bitmap object index enabled did not work correctly. This has been corrected. * Git 2.0 had a regression which broke (rarely used) "git diff-tree -t". This has been corrected. * "git log --pretty/format=" with an empty format string did not mean the more obvious "No output whatsoever" but "Use default format", which was counterintuitive. Now it means "nothing shown for the log message part". * "git -c section.var command" and "git -c section.var= command" should pass the configuration differently (the former should be a boolean true, the latter should be an empty string), but they didn't work that way. Now it does. * Applying a patch not generated by Git in a subdirectory used to check the whitespace breakage using the attributes for incorrect paths. Also whitespace checks were performed even for paths excluded via "git apply --exclude=<path>" mechanism. * "git bundle create" with date-range specification were meant to exclude tags outside the range, but it did not work correctly. * "git add x" where x that used to be a directory has become a symbolic link to a directory misbehaved. * The prompt script checked $GIT_DIR/ref/stash file to see if there is a stash, which was a no-no. * "git checkout -m" did not switch to another branch while carrying the local changes forward when a path was deleted from the index. * With sufficiently long refnames, fast-import could have overflown an on-stack buffer. * After "pack-refs --prune" packed refs at the top-level, it failed to prune them. * "git gc --auto" triggered from "git fetch --quiet" was not quiet. - -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - -- Albino binoanb.eti.br -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJUHMpzAAoJEMeHw9hY0iHaQQgP/jN/52kntQEOM2U/YGBssqmi lZiu3s3T/AwsCFS+RHUuln3tLeypAyGYKMXOgZw4gKmEJSyxMLvIg0EqRhcIYIfS 7fddFa4YI5ASRssZyXlsbPVQ6DNPZE9+VGLCvREJWIhBtM4MWpqxkv8+TZlojM8C hwJmoo7BmQj7NZn6cm4MnefNG75e6i3Mxyi55EsN6gBcWPEybf5ptHxFA5erT4YW 6eh8Xpm2YYxPD/r+ExyiE+F2ckbE8AD7TgOcS+WETiS+4H1C9D1t6PXeKBNqu2KG yZfFfuDay9ESfyniYYJigjt+lUIMzgziPIAgcLfE3rTQEDm0HFpgEjT76LAnkeFy E2UdjSgevdFQ7NfONTlztLEstZ9eMoXmPe/lxFBuVnHPtx0aC595y5nrUbXoo4PN SqVcIViF8QeNdmEi/YsA7ysI6uvxHdhbo6p94UyxWF+EXDGuD88z1XHwbjrOvhWG emlQbljaiVLK6oYRxqOY2unPq3MmO5C/tQtn+mwIx59sqK0Al9+6HXKFpP+NhPdC rJyRJJLHk4AS03riN8tkRP/YCjGD2GlLZup/pdMSn8CS6oHZ3LzSRdVJfM5OEZvX w8VjCPnKttv+gGV0iRkutIfrNe8UCqjw7DUfE6lL55LEdrrnwovMAOM0101bLujc 1p2LN5qY5BhT8Cj+lPy/ =ig4i -----END PGP SIGNATURE-----
