Documentation / RelNotes-1.5.4.5.txton commit merge-recursive --renormalize (7610fa5)
   1GIT v1.5.4.5 Release Notes
   2==========================
   3
   4Fixes since v1.5.4.4
   5--------------------
   6
   7 * "git fetch there" when the URL information came from the Cogito style
   8   branches/there file did not update refs/heads/there (regression in
   9   1.5.4).
  10
  11 * Bogus refspec configuration such as "remote.there.fetch = =" were not
  12   detected as errors (regression in 1.5.4).
  13
  14 * You couldn't specify a custom editor whose path contains a whitespace
  15   via GIT_EDITOR (and core.editor).
  16
  17 * The subdirectory filter to "git filter-branch" mishandled a history
  18   where the subdirectory becomes empty and then later becomes non-empty.
  19
  20 * "git shortlog" gave an empty line if the original commit message was
  21   malformed (e.g. a botched import from foreign SCM).  Now it finds the
  22   first non-empty line and uses it for better information.
  23
  24 * When the user fails to give a revision parameter to "git svn", an error
  25   from the Perl interpreter was issued because the script lacked proper
  26   error checking.
  27
  28 * After "git rebase" stopped due to conflicts, if the user played with
  29   "git reset" and friends, "git rebase --abort" failed to go back to the
  30   correct commit.
  31
  32 * Additional work trees prepared with git-new-workdir (in contrib/) did
  33   not share git-svn metadata directory .git/svn with the original.
  34
  35 * "git-merge-recursive" did not mark addition of the same path with
  36   different filemodes correctly as a conflict.
  37
  38 * "gitweb" gave malformed URL when pathinfo stype paths are in use.
  39
  40 * "-n" stands for "--no-tags" again for "git fetch".
  41
  42 * "git format-patch" did not detect the need to add 8-bit MIME header
  43   when the user used format.header configuration.
  44
  45 * "rev~" revision specifier used to mean "rev", which was inconsistent
  46   with how "rev^" worked.  Now "rev~" is the same as "rev~1" (hence it
  47   also is the same as "rev^1"), and "rev~0" is the same as "rev^0"
  48   (i.e. it has to be a commit).
  49
  50 * "git quiltimport" did not grok empty lines, lines in "file -pNNN"
  51   format to specify the prefix levels and lines with trailing comments.
  52
  53 * "git rebase -m" triggered pre-commit verification, which made
  54   "rebase --continue" impossible.
  55
  56As usual, it also comes with many documentation fixes and clarifications.