Documentation / RelNotes / 1.7.12.1.txton commit Second half of the fifth batch for 1.8.0 (53284de)
   1Git 1.7.12.1 Release Notes
   2==========================
   3
   4Fixes since v1.7.12
   5-------------------
   6
   7 * "ciabot" script (in contrib/) has been updated with extensive
   8   documentation.
   9
  10 * The "--rebase" option to "git pull" can be abbreviated to "-r",
  11   but we didn't document it.
  12
  13 * It was generally understood that "--long-option"s to many of our
  14   subcommands can be abbreviated to the unique prefix, but it was not
  15   easy to find it described for new readers of the documentation set.
  16
  17 * The "--topo-order", "--date-order" (and the lack of either means
  18   the default order) options to "rev-list" and "log" family of
  19   commands were poorly described in the documentation.
  20
  21 * Older parts of the documentation described as if having a regular
  22   file in .git/refs/ hierarchy were the only way to have branches and
  23   tags, which is not true for quite some time.
  24
  25 * A utility shell function test_seq has been added as a replacement
  26   for the 'seq' utility found on some platforms.
  27
  28 * Compatibility wrapper to learn the maximum number of file
  29   descriptors we can open around sysconf(_SC_OPEN_MAX) and
  30   getrlimit(RLIMIT_NO_FILE) has been introduced for portability.
  31
  32 * We used curl_easy_strerror() without checking version of cURL,
  33   breaking the build for versions before curl 7.12.0.
  34
  35 * Code to work around MacOS X UTF-8 gotcha has been cleaned up.
  36
  37 * Fallback 'getpass' implementation made unportable use of stdio API.
  38
  39 * "git commit --amend" let the user edit the log message and then
  40   died when the human-readable committer name was given
  41   insufficiently by getpwent(3).
  42
  43 * Some capabilities were asked by fetch-pack even when upload-pack
  44   did not advertise that they are available.  fetch-pack has been
  45   fixed not to do so.
  46
  47 * "git prune" without "-v" used to warn about leftover temporary
  48   files (which is an indication of an earlier aborted operation).
  49
  50 * The reflog entries left by "git rebase" and "git rebase -i" were
  51   inconsistent (the interactive one gave an abbreviated object name).
  52
  53 * When the user exports a non-default IFS without HT, scripts that
  54   rely on being able to parse "ls-files -s | while read a b c..."
  55   started to fail.  Protect them from such a misconfiguration.
  56
  57 * When "git push" triggered the automatic gc on the receiving end, a
  58   message from "git prune" that said it was removing cruft leaked to
  59   the standard output, breaking the communication protocol.
  60
  61 * "git diff" had a confusion between taking data from a path in the
  62   working tree and taking data from an object that happens to have
  63   name 0{40} recorded in a tree.
  64
  65 * "git send-email" did not unquote encoded words that appear on the
  66   header correctly, and lost "_" from strings.
  67
  68 * When the user gives an argument that can be taken as both a
  69   revision name and a pathname without disambiguating with "--", we
  70   used to give a help message "Use '--' to separate".  The message
  71   has been clarified to show where that '--' goes on the command
  72   line.
  73
  74 * "gitweb" when used with PATH_INFO failed to notice directories with
  75   SP (and other characters that need URL-style quoting) in them.