Documentation / RelNotes / 2.13.3.txton commit worktree: disallow adding same path multiple times (cb56f55)
   1Git v2.13.3 Release Notes
   2=========================
   3
   4Fixes since v2.13.2
   5-------------------
   6
   7 * The "collision detecting" SHA-1 implementation shipped with 2.13.2
   8   was still broken on some platforms.  Update to the upstream code
   9   again to take their fix.
  10
  11 * The 'diff-highlight' program (in contrib/) has been restructured
  12   for easier reuse by an external project 'diff-so-fancy'.
  13
  14 * "git mergetool" learned to work around a wrapper MacOS X adds
  15   around underlying meld.
  16
  17 * An example in documentation that does not work in multi worktree
  18   configuration has been corrected.
  19
  20 * The pretty-format specifiers like '%h', '%t', etc. had an
  21   optimization that no longer works correctly.  In preparation/hope
  22   of getting it correctly implemented, first discard the optimization
  23   that is broken.
  24
  25 * The code to pick up and execute command alias definition from the
  26   configuration used to switch to the top of the working tree and
  27   then come back when the expanded alias was executed, which was
  28   unnecessarilyl complex.  Attempt to simplify the logic by using the
  29   early-config mechanism that does not chdir around.
  30
  31 * "git add -p" were updated in 2.12 timeframe to cope with custom
  32   core.commentchar but the implementation was buggy and a
  33   metacharacter like $ and * did not work.
  34
  35 * Fix a recent regression to "git rebase -i" and add tests that would
  36   have caught it and others.
  37
  38 * An unaligned 32-bit access in pack-bitmap code ahs been corrected.
  39
  40 * Tighten error checks for invalid "git apply" input.
  41
  42 * The split index code did not honor core.sharedrepository setting
  43   correctly.
  44
  45 * The Makefile rule in contrib/subtree for building documentation
  46   learned to honour USE_ASCIIDOCTOR just like the main documentation
  47   set does.
  48
  49 * A few tests that tried to verify the contents of push certificates
  50   did not use 'git rev-parse' to formulate the line to look for in
  51   the certificate correctly.
  52
  53 * After "git branch --move" of the currently checked out branch, the
  54   code to walk the reflog of HEAD via "log -g" and friends
  55   incorrectly stopped at the reflog entry that records the renaming
  56   of the branch.
  57
  58 * The rewrite of "git branch --list" using for-each-ref's internals
  59   that happened in v2.13 regressed its handling of color.branch.local;
  60   this has been fixed.
  61
  62Also contains various documentation updates and code clean-ups.