1 GIT v1.6.6 Release Notes
2 ========================
4 In git 1.7.0, which is planned to be the release after 1.6.6, "git
5 push" into a branch that is currently checked out will be refused by
8 You can choose what should happen upon such a push by setting the
9 configuration variable receive.denyCurrentBranch in the receiving
12 Also, "git push $there :$killed" to delete the branch $killed in a remote
13 repository $there, when $killed branch is the current branch pointed at by
14 its HEAD, will be refused by default.
16 You can choose what should happen upon such a push by setting the
17 configuration variable receive.denyDeleteCurrent in the receiving
20 To ease the transition plan, the receiving repository of such a
21 push running this release will issue a big warning when the
22 configuration variable is missing. Please refer to:
24 http://git.or.cz/gitwiki/GitFaq#non-bare
25 http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
27 for more details on the reason why this change is needed and the
39 (usability, bells and whistles)
41 * "git log --decorate" shows the location of HEAD as well.
48 All of the fixes in v1.6.5.X maintenance series are included in this
49 release, unless otherwise noted.
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"
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.