| blob | 2ab2328316a8b52613eacfe8e0b865ec69ee3154 |
1 GIT v1.6.3 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
17 transition plan.
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.
26 Updates since v1.6.2
27 --------------------
29 (subsystems)
31 (performance)
33 (usability, bells and whistles)
36 Fixes since v1.6.2
37 ------------------
39 All of the fixes in v1.6.2.X maintenance series are included in this
40 release, unless otherwise noted.
42 Here are fixes that this release has, but have not been backported to
43 v1.6.2.X series.