Documentation / RelNotes / 1.7.10.1.txton commit Merge branch 'cb/http-multi-curl-auth' (157a476)
   1Git v1.7.10.1 Release Notes
   2===========================
   3
   4Fixes since v1.7.10
   5-------------------
   6
   7 * "git add -p" is not designed to deal with unmerged paths but did
   8   not exclude them and tried to apply funny patches only to fail.
   9
  10 * When PATH contains an unreadable directory, alias expansion code
  11   did not kick in, and failed with an error that said "git-subcmd"
  12   was not found.
  13
  14 * "git clean -d -f" (not "-d -f -f") is supposed to protect nested
  15   working trees of independent git repositories that exist in the
  16   current project working tree from getting removed, but the
  17   protection applied only to such working trees that are at the
  18   top-level of the current project by mistake.
  19
  20 * "git commit --author=$name" did not tell the name that was being
  21   recorded in the resulting commit to hooks, even though it does do
  22   so when the end user overrode the authorship via the
  23   "GIT_AUTHOR_NAME" environment variable.
  24
  25 * When "git commit --template F" errors out because the user did not
  26   touch the message, it claimed that it aborts due to "empty
  27   message", which was utterly wrong.
  28
  29 * The regexp configured with diff.wordregex was incorrectly reused
  30   across files.
  31
  32 * An age-old corner case bug in combine diff (only triggered with -U0
  33   and the hunk at the beginning of the file needs to be shown) has
  34   been fixed.
  35
  36 * Rename detection logic used to match two empty files as renames
  37   during merge-recursive, leading to unnatural mismerges.
  38
  39 * Running "notes merge --commit" failed to perform correctly when run
  40   from any directory inside $GIT_DIR/.  When "notes merge" stops with
  41   conflicts, $GIT_DIR/NOTES_MERGE_WORKTREE is the place a user edits
  42   to resolve it.
  43
  44 * The 'push to upstream' implementation was broken in some corner
  45   cases. "git push $there" without refspec, when the current branch
  46   is set to push to a remote different from $there, used to push to
  47   $there using the upstream information to a remote unreleated to
  48   $there.
  49
  50Also contains minor fixes and documentation updates.