Documentation / RelNotes-1.6.6.txton commit Merge branch 'tf/doc-pt-br' (178071b)
   1GIT v1.6.6 Release Notes
   2========================
   3
   4In git 1.7.0, which is planned to be the release after 1.6.6, "git
   5push" into a branch that is currently checked out will be refused by
   6default.
   7
   8You can choose what should happen upon such a push by setting the
   9configuration variable receive.denyCurrentBranch in the receiving
  10repository.
  11
  12Also, "git push $there :$killed" to delete the branch $killed in a remote
  13repository $there, when $killed branch is the current branch pointed at by
  14its HEAD, will be refused by default.
  15
  16You can choose what should happen upon such a push by setting the
  17configuration variable receive.denyDeleteCurrent in the receiving
  18repository.
  19
  20To ease the transition plan, the receiving repository of such a
  21push running this release will issue a big warning when the
  22configuration variable is missing.  Please refer to:
  23
  24  http://git.or.cz/gitwiki/GitFaq#non-bare
  25  http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
  26
  27for more details on the reason why this change is needed and the
  28transition plan.
  29
  30Updates since v1.6.5
  31--------------------
  32
  33(subsystems)
  34
  35(portability)
  36
  37(performance)
  38
  39(usability, bells and whistles)
  40
  41 * "git log --decorate" shows the location of HEAD as well.
  42
  43(developers)
  44
  45Fixes since v1.6.5
  46------------------
  47
  48All of the fixes in v1.6.5.X maintenance series are included in this
  49release, unless otherwise noted.
  50
  51 * "git apply" and "git diff" (including patch output from "git log -p")
  52   now flags trailing blank lines as whitespace errors correctly (only
  53   "apply --whitespace=fix" stripped them but "apply --whitespace=warn"
  54   did not even warn).
  55
  56 * Two whitespace error classes, 'blank-at-eof' and 'blank-at-eol', have
  57   been introduced (settable by core.whitespace configuration variable and
  58   whitespace attribute).  The 'trailing-space' whitespace error class has
  59   become a short-hand to cover both of these and there is no behaviour
  60   change for existing set-ups.