1 GIT v1.6.4 Release Notes
2 ========================
4 With the next major release, "git push" into a branch that is
5 currently checked out will be refused by default. You can choose
6 what should happen upon such a push by setting the configuration
7 variable receive.denyCurrentBranch in the receiving repository.
9 To ease the transition plan, the receiving repository of such a
10 push running this release will issue a big warning when the
11 configuration variable is missing. Please refer to:
13 http://git.or.cz/gitwiki/GitFaq#non-bare
14 http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
16 for more details on the reason why this change is needed and the
19 For a similar reason, "git push $there :$killed" to delete the branch
20 $killed in a remote repository $there, if $killed branch is the current
21 branch pointed at by its HEAD, gets a large warning. You can choose what
22 should happen upon such a push by setting the configuration variable
23 receive.denyDeleteCurrent in the receiving repository.
25 When the user does not tell "git push" what to push, it has always
26 pushed matching refs. For some people it is unexpected, and a new
27 configuration variable push.default has been introduced to allow
28 changing a different default behaviour. To advertise the new feature,
29 a big warning is issued if this is not configured and a git push without
30 arguments is attempted.
40 (usability, bells and whistles)
48 All of the fixes in v1.6.3.X maintenance series are included in this
49 release, unless otherwise noted.
51 Here are fixes that this release has, but have not been backported to
57 echo O=$(git describe master)
59 git shortlog --no-merges $O..master ^maint