Documentation / RelNotes-1.7.0.txton commit Merge branch 'ap/merge-backend-opts' (fcb2a7e)
   1Git v1.7.0 Release Notes
   2========================
   3
   4Notes on behaviour change
   5-------------------------
   6
   7 * "git push" into a branch that is currently checked out (i.e. pointed by
   8   HEAD in a repository that is not bare) is refused by default.
   9
  10   Similarly, "git push $there :$killed" to delete the branch $killed
  11   in a remote repository $there, when $killed branch is the current
  12   branch pointed at by its HEAD, will be refused by default.
  13
  14   Setting the configuration variables receive.denyCurrentBranch and
  15   receive.denyDeleteCurrent to 'ignore' in the receiving repository
  16   can be used to override these safety features.
  17
  18 * "git send-email" does not make deep threads by default when sending a
  19   patch series with more than two messages.  All messages will be sent
  20   as a reply to the first message, i.e. cover letter.
  21
  22   It has been possible to configure send-email to send "shallow thread"
  23   by setting sendemail.chainreplyto configuration variable to false.  The
  24   only thing this release does is to change the default when you haven't
  25   configured that variable.
  26
  27 * "git status" is not "git commit --dry-run" anymore.  This change does
  28   not affect you if you run the command without pathspec.
  29
  30 * "git diff" traditionally treated various "ignore whitespace" options
  31   only as a way to filter the patch output.  "git diff --exit-code -b"
  32   exited with non-zero status even if all changes were about changing the
  33   ammount of whitespace and nothing else.  and "git diff -b" showed the
  34   "diff --git" header line for such a change without patch text.
  35
  36   In this release, the "ignore whitespaces" options affect the semantics
  37   of the diff operation.  A change that does not affect anything but
  38   whitespaces is reported with zero exit status when run with
  39   --exit-code, and there is no "diff --git" header for such a change.
  40
  41
  42Updates since v1.6.6
  43--------------------
  44
  45(subsystems)
  46
  47 * "git fast-import" updates; adds "option" and "feature" to detect the
  48   mismatch between fast-import and the frontends that produce the input
  49   stream.
  50
  51(portability)
  52
  53 * Some more MSVC portability patches for msysgit port.
  54
  55 * Minimum Pthreads emulation for msysgit port.
  56
  57(performance)
  58
  59 * More performance improvement patches for msysgit port.
  60
  61(usability, bells and whistles)
  62
  63 * More commands learned "--quiet" and "--[no-]progress" options.
  64
  65 * Various commands given by the end user (e.g. diff.type.textconv,
  66   and GIT_EDITOR) can be specified with command line arguments.  E.g. it
  67   is now possible to say "[diff "utf8doc"] textconv = nkf -w".
  68
  69 * "sparse checkout" feature allows only part of the work tree to be
  70   checked out.
  71
  72 * HTTP transfer can use authentication scheme other than basic
  73   (i.e./e.g. digest).
  74
  75 * Switching from a version of superproject that used to have a submodule
  76   to another version of superproject that no longer has it did not remove
  77   the submodule directory when it should (namely, when you are not
  78   interested in the submodule at all and didn't clone/checkout).
  79
  80 * "git checkout A...B" is a way to detach HEAD at the merge base between
  81   A and B.
  82
  83 * "git commit --date='<date>'" can be used to override the author date
  84   just like "git commit --author='<name> <email>'" can be used to
  85   override the author identity.
  86
  87 * "git commit --no-status" can be used to omit the listing of the index
  88   and the work tree status in the editor used to prepare the log message.
  89
  90 * "git fetch --all" can now be used in place of "git remote update".
  91
  92 * "git push" learned "git push origin --delete branch", a syntactic sugar
  93   for "git push origin :branch".
  94
  95 * "git rebase --onto A...B" means the history is replayed on top of the
  96   merge base between A and B.
  97
  98 * Use of "git reset --merge" has become easier when resetting away a
  99   conflicted mess left in the work tree.
 100
 101 * "git rerere" had rerere.autoupdate configuration but there was no way
 102   to countermand it from the command line; --no-rerere-autoupdate option
 103   given to "merge", "revert", etc. fixes this.
 104
 105 * "git status" learned "-s(hort)" output format.
 106
 107(developers)
 108
 109 * The infrastructure to build foreign SCM interface has been updated.
 110
 111
 112Fixes since v1.6.6
 113------------------
 114
 115All of the fixes in v1.6.6.X maintenance series are included in this
 116release, unless otherwise noted.
 117
 118--
 119exec >/var/tmp/1
 120O=v1.6.6-263-ge33fd3c
 121echo O=$(git describe master)
 122git shortlog --no-merges $O..master ^maint