Documentation / RelNotes / 2.3.1.txton commit Merge branch 'mg/gpg-parse-tighten' (0256189)
   1Git v2.3.1 Release Notes
   2========================
   3
   4Fixes since v2.3
   5----------------
   6
   7 * The interactive "show a list and let the user choose from it"
   8   interface "add -i" used showed and prompted to the user even when
   9   the candidate list was empty, against which the only "choice" the
  10   user could have made was to choose nothing.
  11
  12 * "git apply --whitespace=fix" used to under-allocate the memory
  13   when the fix resulted in a longer text than the original patch.
  14
  15 * "git log --help" used to show rev-list options that are irrelevant
  16   to the "log" command.
  17
  18 * The error message from "git commit", when a non-existing author
  19   name was given as value to the "--author=" parameter, has been
  20   reworded to avoid misunderstanding.
  21
  22 * A broken pack .idx file in the receiving repository prevented the
  23   dumb http transport from fetching a good copy of it from the other
  24   side.
  25
  26 * The documentation incorrectly said that C(opy) and R(ename) are the
  27   only ones that can be followed by the score number in the output in
  28   the --raw format.
  29
  30 * Fix a misspelled conditional that is always true.
  31
  32 * Code to read branch name from various files in .git/ directory
  33   would have misbehaved if the code to write them left an empty file.
  34
  35 * The "git push" documentation made the "--repo=<there>" option
  36   easily misunderstood.
  37
  38 * After attempting and failing a password-less authentication
  39   (e.g. kerberos), libcURL refuses to fall back to password based
  40   Basic authentication without a bit of help/encouragement.
  41
  42 * Setting diff.submodule to 'log' made "git format-patch" produce
  43   broken patches.
  44
  45 * "git rerere" (invoked internally from many mergy operations) did
  46   not correctly signal errors when told to update the working tree
  47   files and failed to do so for whatever reason.
  48
  49 * "git blame HEAD -- missing" failed to correctly say "HEAD" when it
  50   tried to say "No such path 'missing' in HEAD".
  51
  52Also contains typofixes, documentation updates and trivial code clean-ups.