Documentation / RelNotes / 1.6.1.1.txton commit Merge branch 'py/call-do-quit-before-exit' of github.com:gitster/git-gui into py/git-gui-do-quit (0d88f3d)
   1GIT v1.6.1.1 Release Notes
   2==========================
   3
   4Fixes since v1.6.1
   5------------------
   6
   7* "git add frotz/nitfol" when "frotz" is a submodule should have errored
   8  out, but it didn't.
   9
  10* "git apply" took file modes from the patch text and updated the mode
  11  bits of the target tree even when the patch was not about mode changes.
  12
  13* "git bisect view" on Cygwin did not launch gitk
  14
  15* "git checkout $tree" did not trigger an error.
  16
  17* "git commit" tried to remove COMMIT_EDITMSG from the work tree by mistake.
  18
  19* "git describe --all" complained when a commit is described with a tag,
  20  which was nonsense.
  21
  22* "git diff --no-index --" did not trigger no-index (aka "use git-diff as
  23  a replacement of diff on untracked files") behaviour.
  24
  25* "git format-patch -1 HEAD" on a root commit failed to produce patch
  26  text.
  27
  28* "git fsck branch" did not work as advertised; instead it behaved the same
  29  way as "git fsck".
  30
  31* "git log --pretty=format:%s" did not handle a multi-line subject the
  32  same way as built-in log listers (i.e. shortlog, --pretty=oneline, etc.)
  33
  34* "git daemon", and "git merge-file" are more careful when freopen fails
  35  and barf, instead of going on and writing to unopened filehandle.
  36
  37* "git http-push" did not like some RFC 4918 compliant DAV server
  38  responses.
  39
  40* "git merge -s recursive" mistakenly overwritten an untracked file in the
  41  work tree upon delete/modify conflict.
  42
  43* "git merge -s recursive" didn't leave the index unmerged for entries with
  44  rename/delete conflicts.
  45
  46* "git merge -s recursive" clobbered untracked files in the work tree.
  47
  48* "git mv -k" with more than one erroneous paths misbehaved.
  49
  50* "git read-tree -m -u" hence branch switching incorrectly lost a
  51  subdirectory in rare cases.
  52
  53* "git rebase -i" issued an unnecessary error message upon a user error of
  54  marking the first commit to be "squash"ed.
  55
  56* "git shortlog" did not format a commit message with multi-line
  57  subject correctly.
  58
  59Many documentation updates.