1Git v1.7.10.1 Release Notes 2=========================== 3 4Additions since v1.7.10 5----------------------- 6 7Localization message files for Danish and German have been added. 8 9 10Fixes since v1.7.10 11------------------- 12 13 * "git add -p" is not designed to deal with unmerged paths but did 14 not exclude them and tried to apply funny patches only to fail. 15 16 * "git blame" started missing quite a few changes from the origin 17 since we stopped using the diff minimalization by default in v1.7.2 18 era. 19 20 * When PATH contains an unreadable directory, alias expansion code 21 did not kick in, and failed with an error that said "git-subcmd" 22 was not found. 23 24 * "git clean -d -f" (not "-d -f -f") is supposed to protect nested 25 working trees of independent git repositories that exist in the 26 current project working tree from getting removed, but the 27 protection applied only to such working trees that are at the 28 top-level of the current project by mistake. 29 30 * "git commit --author=$name" did not tell the name that was being 31 recorded in the resulting commit to hooks, even though it does do 32 so when the end user overrode the authorship via the 33 "GIT_AUTHOR_NAME" environment variable. 34 35 * When "git commit --template F" errors out because the user did not 36 touch the message, it claimed that it aborts due to "empty 37 message", which was utterly wrong. 38 39 * The regexp configured with diff.wordregex was incorrectly reused 40 across files. 41 42 * An age-old corner case bug in combine diff (only triggered with -U0 43 and the hunk at the beginning of the file needs to be shown) has 44 been fixed. 45 46 * Rename detection logic used to match two empty files as renames 47 during merge-recursive, leading to unnatural mismerges. 48 49 * The parser in "fast-import" did not diagnose ":9" style references 50 that is not followed by required SP/LF as an error. 51 52 * When "git fetch" encounters repositories with too many references, 53 the command line of "fetch-pack" that is run by a helper 54 e.g. remote-curl, may fail to hold all of them. Now such an 55 internal invocation can feed the references through the standard 56 input of "fetch-pack". 57 58 * "git fetch" that recurses into submodules on demand did not check 59 if it needs to go into submodules when non branches (most notably, 60 tags) are fetched. 61 62 * "log -p --graph" used with "--stat" had a few formatting error. 63 64 * Running "notes merge --commit" failed to perform correctly when run 65 from any directory inside $GIT_DIR/. When "notes merge" stops with 66 conflicts, $GIT_DIR/NOTES_MERGE_WORKTREE is the place a user edits 67 to resolve it. 68 69 * The 'push to upstream' implementation was broken in some corner 70 cases. "git push $there" without refspec, when the current branch 71 is set to push to a remote different from $there, used to push to 72 $there using the upstream information to a remote unreleated to 73 $there. 74 75 * Giving "--continue" to a conflicted "rebase -i" session skipped a 76 commit that only results in changes to submodules. 77 78Also contains minor fixes and documentation updates.