{"thread":{"id":"30511","subject":"[ANNOUNCE] Git 1.7.10.2","startedAt":"2012-05-11T20:49:38Z","lastAt":"2012-05-11T20:49:38Z","messageCount":1,"participants":["Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"191417","messageId":"7v4nrml9y5.fsf@alter.siamese.dyndns.org","threadId":"30511","inReplyTo":null,"subject":"[ANNOUNCE] Git 1.7.10.2","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-05-11T20:49:38Z","receivedAt":"2012-05-11T20:49:38Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"The latest maintenance release Git 1.7.10.2 is now available at\nthe usual places.\n\nThe release tarballs are found at:\n\n    http://code.google.com/p/git-core/downloads/list\n\nand their SHA-1 checksums are:\n\ne4b7f746ff4e356baaddcad0b2911376efde031b  git-1.7.10.2.tar.gz\n004a2bf989b935657e2e1e6000a748d83657649f  git-htmldocs-1.7.10.2.tar.gz\n6cc3f80185bdd1a608cf373b05313b2adc82b898  git-manpages-1.7.10.2.tar.gz\n\nAlso the following public repositories all have a copy of the v1.7.10.2\ntag and the maint branch that the tag points at:\n\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 v1.7.10.2 Release Notes\n===========================\n\nFixes since v1.7.10.1\n---------------------\n\n * The test scaffolding for git-daemon was flaky.\n\n * The test scaffolding for fast-import was flaky.\n\n * The filesystem boundary was not correctly reported when .git directory\n   discovery stopped at a mount point.\n\n * HTTP transport that requires authentication did not work correctly when\n   multiple connections are used simultaneously.\n\n * Minor memory leak during unpack_trees (hence \"merge\" and \"checkout\"\n   to check out another branch) has been plugged.\n\n * In the older days, the header \"Conflicts:\" in \"cherry-pick\" and \"merge\"\n   was separated by a blank line from the list of paths that follow for\n   readability, but when \"merge\" was rewritten in C, we lost it by\n   mistake. Remove the newline from \"cherry-pick\" to make them match\n   again.\n\n * The command line parser choked \"git cherry-pick $name\" when $name can\n   be both revision name and a pathname, even though $name can never be a\n   path in the context of the command.\n\n * The \"include.path\" facility in the configuration mechanism added in\n   1.7.10 forgot to interpret \"~/path\" and \"~user/path\" as it should.\n\n * \"git config --rename-section\" to rename an existing section into a\n   bogus one did not check the new name.\n\n * The \"diff --no-index\" codepath used limited-length buffers, risking\n   pathnames getting truncated.  Update it to use the strbuf API.\n\n * The report from \"git fetch\" said \"new branch\" even for a non branch\n   ref.\n\n * The http-backend (the server side of the smart http transfer) used\n   to overwrite GIT_COMMITTER_NAME and GIT_COMMITTER_EMAIL with the\n   value obtained from REMOTE_USER unconditionally, making it\n   impossible for the server side site-specific customization to use\n   different identity sources to affect the names logged. It now uses\n   REMOTE_USER only as a fallback value.\n\n * \"log --graph\" was not very friendly with \"--stat\" option and its\n   output had line breaks at wrong places.\n\n * Octopus merge strategy did not reduce heads that are recorded in the\n   final commit correctly.\n\n * \"git push\" over smart-http lost progress output a few releases ago;\n   this release resurrects it.\n\n * The error and advice messages given by \"git push\" when it fails due\n   to non-ff were not very helpful to new users; it has been broken\n   into three cases, and each is given a separate advice message.\n\n * The insn sheet given by \"rebase -i\" did not make it clear that the\n   insn lines can be re-ordered to affect the order of the commits in\n   the resulting history.\n\n * \"git repack\" used to write out unreachable objects as loose objects\n   when repacking, even if such loose objects will immediately pruned\n   due to its age.\n\n * A contrib script \"rerere-train\" did not work out of the box unless\n   user futzed with her $PATH.\n\n * \"git rev-parse --show-prefix\" used to emit nothing when run at the\n   top-level of the working tree, but now it gives a blank line.\n\n * The i18n of error message \"git stash save\" was not properly done.\n\n * \"git submodule\" used a sed script that some platforms mishandled.\n\n * When using a Perl script on a system where \"perl\" found on user's\n   $PATH could be ancient or otherwise broken, we allow builders to\n   specify the path to a good copy of Perl with $PERL_PATH.  The\n   gitweb test forgot to use that Perl when running its test.\n\nAlso contains minor fixes and documentation updates.\n"}]}