Documentation / RelNotes / 2.7.3.txton commit branch: add worktree info on verbose output (6e93814)
   1Git v2.7.3 Release Notes
   2========================
   3
   4Fixes since v2.7.2
   5------------------
   6
   7 * Traditionally, the tests that try commands that work on the
   8   contents in the working tree were named with "worktree" in their
   9   filenames, but with the recent addition of "git worktree"
  10   subcommand, whose tests are also named similarly, it has become
  11   harder to tell them apart.  The traditional tests have been renamed
  12   to use "work-tree" instead in an attempt to differentiate them.
  13
  14 * Many codepaths forget to check return value from git_config_set();
  15   the function is made to die() to make sure we do not proceed when
  16   setting a configuration variable failed.
  17
  18 * Handling of errors while writing into our internal asynchronous
  19   process has been made more robust, which reduces flakiness in our
  20   tests.
  21
  22 * "git show 'HEAD:Foo[BAR]Baz'" did not interpret the argument as a
  23   rev, i.e. the object named by the the pathname with wildcard
  24   characters in a tree object.
  25
  26 * "git rev-parse --git-common-dir" used in the worktree feature
  27   misbehaved when run from a subdirectory.
  28
  29 * The "v(iew)" subcommand of the interactive "git am -i" command was
  30   broken in 2.6.0 timeframe when the command was rewritten in C.
  31
  32 * "git merge-tree" used to mishandle "both sides added" conflict with
  33   its own "create a fake ancestor file that has the common parts of
  34   what both sides have added and do a 3-way merge" logic; this has
  35   been updated to use the usual "3-way merge with an empty blob as
  36   the fake common ancestor file" approach used in the rest of the
  37   system.
  38
  39 * The memory ownership rule of fill_textconv() API, which was a bit
  40   tricky, has been documented a bit better.
  41
  42 * The documentation did not clearly state that the 'simple' mode is
  43   now the default for "git push" when push.default configuration is
  44   not set.
  45
  46 * Recent versions of GNU grep are pickier when their input contains
  47   arbitrary binary data, which some of our tests uses.  Rewrite the
  48   tests to sidestep the problem.
  49
  50 * A helper function "git submodule" uses since v2.7.0 to list the
  51   modules that match the pathspec argument given to its subcommands
  52   (e.g. "submodule add <repo> <path>") has been fixed.
  53
  54 * "git config section.var value" to set a value in per-repository
  55   configuration file failed when it was run outside any repository,
  56   but didn't say the reason correctly.
  57
  58 * The code to read the pack data using the offsets stored in the pack
  59   idx file has been made more carefully check the validity of the
  60   data in the idx.
  61
  62Also includes documentation and test updates.