{"thread":{"id":"30390","subject":"[ANNOUNCE] Git 1.7.10.1","startedAt":"2012-05-02T05:12:46Z","lastAt":"2012-05-02T05:12:46Z","messageCount":1,"participants":["Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"190520","messageId":"7vk40vjhdd.fsf@alter.siamese.dyndns.org","threadId":"30390","inReplyTo":null,"subject":"[ANNOUNCE] Git 1.7.10.1","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-05-02T05:12:46Z","receivedAt":"2012-05-02T05:12:46Z","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.1 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\n870361f93fad7999f121bc7bc91a743feda68bdb  git-1.7.10.1.tar.gz\n29b79312482f9aaf92ee3d970caee5ed8ab96bba  git-htmldocs-1.7.10.1.tar.gz\n5bff761bc40a6b3cfe35ba824357dcf611dbd5d2  git-manpages-1.7.10.1.tar.gz\n\nAlso the following public repositories all have a copy of the v1.7.10.1\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.1 Release Notes\n===========================\n\nAdditions since v1.7.10\n-----------------------\n\nLocalization message files for Danish and German have been added.\n\n\nFixes since v1.7.10\n-------------------\n\n * \"git add -p\" is not designed to deal with unmerged paths but did\n   not exclude them and tried to apply funny patches only to fail.\n\n * \"git blame\" started missing quite a few changes from the origin\n   since we stopped using the diff minimalization by default in v1.7.2\n   era.\n\n * When PATH contains an unreadable directory, alias expansion code\n   did not kick in, and failed with an error that said \"git-subcmd\"\n   was not found.\n\n * \"git clean -d -f\" (not \"-d -f -f\") is supposed to protect nested\n   working trees of independent git repositories that exist in the\n   current project working tree from getting removed, but the\n   protection applied only to such working trees that are at the\n   top-level of the current project by mistake.\n\n * \"git commit --author=$name\" did not tell the name that was being\n   recorded in the resulting commit to hooks, even though it does do\n   so when the end user overrode the authorship via the\n   \"GIT_AUTHOR_NAME\" environment variable.\n\n * When \"git commit --template F\" errors out because the user did not\n   touch the message, it claimed that it aborts due to \"empty\n   message\", which was utterly wrong.\n\n * The regexp configured with diff.wordregex was incorrectly reused\n   across files.\n\n * An age-old corner case bug in combine diff (only triggered with -U0\n   and the hunk at the beginning of the file needs to be shown) has\n   been fixed.\n\n * Rename detection logic used to match two empty files as renames\n   during merge-recursive, leading to unnatural mismerges.\n\n * The parser in \"fast-import\" did not diagnose \":9\" style references\n   that is not followed by required SP/LF as an error.\n\n * When \"git fetch\" encounters repositories with too many references,\n   the command line of \"fetch-pack\" that is run by a helper\n   e.g. remote-curl, may fail to hold all of them. Now such an\n   internal invocation can feed the references through the standard\n   input of \"fetch-pack\".\n\n * \"git fetch\" that recurses into submodules on demand did not check\n   if it needs to go into submodules when non branches (most notably,\n   tags) are fetched.\n\n * \"log -p --graph\" used with \"--stat\" had a few formatting error.\n\n * Running \"notes merge --commit\" failed to perform correctly when run\n   from any directory inside $GIT_DIR/.  When \"notes merge\" stops with\n   conflicts, $GIT_DIR/NOTES_MERGE_WORKTREE is the place a user edits\n   to resolve it.\n\n * The 'push to upstream' implementation was broken in some corner\n   cases. \"git push $there\" without refspec, when the current branch\n   is set to push to a remote different from $there, used to push to\n   $there using the upstream information to a remote unreleated to\n   $there.\n\n * Giving \"--continue\" to a conflicted \"rebase -i\" session skipped a\n   commit that only results in changes to submodules.\n\nAlso contains minor fixes and documentation updates.\n"}]}