Documentation / RelNotes / 1.7.12.2.txton commit rebase --rebase-merges: root commits can be cousins, too (8fa6eea)
   1Git 1.7.12.2 Release Notes
   2==========================
   3
   4Fixes since v1.7.12.1
   5---------------------
   6
   7 * When "git am" is fed an input that has multiple "Content-type: ..."
   8   header, it did not grok charset= attribute correctly.
   9
  10 * Even during a conflicted merge, "git blame $path" always meant to
  11   blame uncommitted changes to the "working tree" version; make it
  12   more useful by showing cleanly merged parts as coming from the other
  13   branch that is being merged.
  14
  15 * "git blame MAKEFILE" run in a history that has "Makefile" but not
  16   "MAKEFILE" should say "No such file MAKEFILE in HEAD", but got
  17   confused on a case insensitive filesystem and failed to do so.
  18
  19 * "git fetch --all", when passed "--no-tags", did not honor the
  20   "--no-tags" option while fetching from individual remotes (the same
  21   issue existed with "--tags", but combination "--all --tags" makes
  22   much less sense than "--all --no-tags").
  23
  24 * "git log/diff/format-patch --stat" showed the "N line(s) added"
  25   comment in user's locale and caused careless submitters to send
  26   patches with such a line in them to projects whose project language
  27   is not their language, mildly irritating others. Localization to
  28   the line has been disabled for now.
  29
  30 * "git log --all-match --grep=A --grep=B" ought to show commits that
  31   mention both A and B, but when these three options are used with
  32   --author or --committer, it showed commits that mention either A or
  33   B (or both) instead.
  34
  35 * The subcommand to remove the definition of a remote in "git remote"
  36   was named "rm" even though all other subcommands were spelled out.
  37   Introduce "git remote remove" to remove confusion, and keep "rm" as
  38   a backward compatible synonym.
  39
  40Also contains a handful of documentation updates.