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