Documentation / RelNotes-1.5.5.1.txton commit merge-recursive: don't segfault while handling rename clashes (c94736a)
   1GIT v1.5.5.1 Release Notes
   2==========================
   3
   4Fixes since v1.5.5
   5------------------
   6
   7 * "git archive --prefix=$path/" mishandled gitattributes.
   8
   9 * "git fetch -v" that fetches into FETCH_HEAD did not report the summary
  10   the same way as done for updating the tracking refs.
  11
  12 * "git svn" misbehaved when the configuration file customized the "git
  13   log" output format using format.pretty.
  14
  15 * "git submodule status" leaked an unnecessary error message.
  16
  17 * "git log --date-order --topo-order" did not override the earlier
  18   date-order with topo-order as expected.
  19
  20 * "git bisect good $this" did not check the validity of the revision
  21   given properly.
  22
  23 * "url.<there>.insteadOf" did not work correctly.
  24
  25 * "git clean" ran inside subdirectory behaved as if the directory was
  26   explicitly specified for removal by the end user from the top level.
  27
  28 * "git bisect" from a detached head leaked an unnecessary error message.
  29
  30 * "git bisect good $a $b" when $a is Ok but $b is bogus should have
  31   atomically failed before marking $a as good.
  32
  33 * "git fmt-merge-msg" did not clean up leading empty lines from commit
  34   log messages like "git log" family does.
  35
  36 * "git am" recorded a commit with empty Subject: line without
  37   complaining.
  38
  39 * when given a commit log message whose first paragraph consists of
  40   multiple lines, "git rebase" squashed it into a single line.
  41
  42 * "git remote add $bogus_name $url" did not complain properly.
  43
  44Also comes with various documentation updates.