{"thread":{"id":"37599","subject":"[ANNOUNCE] Git v2.1.1","startedAt":"2014-09-19T22:53:45Z","lastAt":"2014-09-19T22:53:45Z","messageCount":1,"participants":["Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"249680","messageId":"xmqqbnqbmdc6.fsf@gitster.dls.corp.google.com","threadId":"37599","inReplyTo":null,"subject":"[ANNOUNCE] Git v2.1.1","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2014-09-19T22:53:45Z","receivedAt":"2014-09-19T22:53:45Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"The latest maintenance release Git v2.1.1 is now available at\nthe usual places.\n\nThe tarballs are found at:\n\n    https://www.kernel.org/pub/software/scm/git/\n\nThe following public repositories all have a copy of the 'v2.1.1'\ntag and the 'maint' branch that the tag points at:\n\n  url = https://kernel.googlesource.com/pub/scm/git/git\n  url = git://repo.or.cz/alt-git.git\n  url = https://code.google.com/p/git-core/\n  url = git://git.sourceforge.jp/gitroot/git-core/git.git\n  url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core\n  url = https://github.com/gitster/git\n\nGit v2.1.1 Release Notes\n========================\n\n * Git 2.0 had a regression where \"git fetch\" into a shallowly\n   cloned repository from a repository with bitmap object index\n   enabled did not work correctly.  This has been corrected.\n\n * Git 2.0 had a regression which broke (rarely used) \"git diff-tree\n   -t\".  This has been corrected.\n\n * \"git log --pretty/format=\" with an empty format string did not\n   mean the more obvious \"No output whatsoever\" but \"Use default\n   format\", which was counterintuitive.  Now it means \"nothing shown\n   for the log message part\".\n\n * \"git -c section.var command\" and \"git -c section.var= command\"\n   should pass the configuration differently (the former should be a\n   boolean true, the latter should be an empty string), but they\n   didn't work that way.  Now it does.\n\n * Applying a patch not generated by Git in a subdirectory used to\n   check the whitespace breakage using the attributes for incorrect\n   paths. Also whitespace checks were performed even for paths\n   excluded via \"git apply --exclude=<path>\" mechanism.\n\n * \"git bundle create\" with date-range specification were meant to\n   exclude tags outside the range, but it did not work correctly.\n\n * \"git add x\" where x that used to be a directory has become a\n   symbolic link to a directory misbehaved.\n\n * The prompt script checked $GIT_DIR/ref/stash file to see if there\n   is a stash, which was a no-no.\n\n * \"git checkout -m\" did not switch to another branch while carrying\n   the local changes forward when a path was deleted from the index.\n\n * With sufficiently long refnames, fast-import could have overflown\n   an on-stack buffer.\n\n * After \"pack-refs --prune\" packed refs at the top-level, it failed\n   to prune them.\n\n * \"git gc --auto\" triggered from \"git fetch --quiet\" was not quiet.\n"}]}