Documentation / RelNotes / 1.8.5.4.txton commit Merge branch 'dk/blame-move-no-reason-for-1-line-context' (7418a6b)
   1Git v1.8.5.4 Release Notes
   2==========================
   3
   4Fixes since v1.8.5.3
   5--------------------
   6
   7 * "git fetch --depth=0" was a no-op, and was silently ignored.
   8   Diagnose it as an error.
   9
  10 * Remote repository URL expressed in scp-style host:path notation are
  11   parsed more carefully (e.g. "foo/bar:baz" is local, "[::1]:/~user" asks
  12   to connect to user's home directory on host at address ::1.
  13
  14 * SSL-related options were not passed correctly to underlying socket
  15   layer in "git send-email".
  16
  17 * "git commit -v" appends the patch to the log message before
  18   editing, and then removes the patch when the editor returned
  19   control. However, the patch was not stripped correctly when the
  20   first modified path was a submodule.
  21
  22 * "git mv A B/", when B does not exist as a directory, should error
  23   out, but it didn't.
  24
  25 * When we figure out how many file descriptors to allocate for
  26   keeping packfiles open, a system with non-working getrlimit() could
  27   cause us to die(), but because we make this call only to get a
  28   rough estimate of how many is available and we do not even attempt
  29   to use up all file descriptors available ourselves, it is nicer to
  30   fall back to a reasonable low value rather than dying.
  31
  32 * "git log --decorate" did not handle a tag pointed by another tag
  33   nicely.
  34
  35 * "git add -A" (no other arguments) in a totally empty working tree
  36   used to emit an error.
  37
  38 * There is no reason to have a hardcoded upper limit of the number of
  39   parents for an octopus merge, created via the graft mechanism, but
  40   there was.
  41
  42 * The implementation of 'git stash $cmd "stash@{...}"' did not quote
  43   the stash argument properly and left it split at IFS whitespace.
  44
  45 * The documentation to "git pull" hinted there is an "-m" option
  46   because it incorrectly shared the documentation with "git merge".
  47
  48Also contains typofixes, documentation updates and trivial code clean-ups.