2009-03-04 09:41:01 +01:00
|
|
|
GIT v1.6.3 Release Notes
|
|
|
|
|
========================
|
|
|
|
|
|
2009-03-05 23:50:00 +01:00
|
|
|
With the next major release, "git push" into a branch that is
|
|
|
|
|
currently checked out will be refused by default. You can choose
|
|
|
|
|
what should happen upon such a push by setting the configuration
|
|
|
|
|
variable receive.denyCurrentBranch in the receiving repository.
|
|
|
|
|
|
|
|
|
|
To ease the transition plan, the receiving repository of such a
|
|
|
|
|
push running this release will issue a big warning when the
|
|
|
|
|
configuration variable is missing. Please refer to:
|
|
|
|
|
|
|
|
|
|
http://git.or.cz/gitwiki/GitFaq#non-bare
|
|
|
|
|
http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
|
|
|
|
|
|
|
|
|
|
for more details on the reason why this change is needed and the
|
|
|
|
|
transition plan.
|
|
|
|
|
|
|
|
|
|
For a similar reason, "git push $there :$killed" to delete the branch
|
|
|
|
|
$killed in a remote repository $there, if $killed branch is the current
|
|
|
|
|
branch pointed at by its HEAD, gets a large warning. You can choose what
|
|
|
|
|
should happen upon such a push by setting the configuration variable
|
|
|
|
|
receive.denyDeleteCurrent in the receiving repository.
|
|
|
|
|
|
|
|
|
|
|
2009-03-04 09:41:01 +01:00
|
|
|
Updates since v1.6.2
|
|
|
|
|
--------------------
|
|
|
|
|
|
|
|
|
|
(subsystems)
|
|
|
|
|
|
|
|
|
|
(performance)
|
|
|
|
|
|
|
|
|
|
(usability, bells and whistles)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fixes since v1.6.2
|
|
|
|
|
------------------
|
|
|
|
|
|
|
|
|
|
All of the fixes in v1.6.2.X maintenance series are included in this
|
|
|
|
|
release, unless otherwise noted.
|
|
|
|
|
|
|
|
|
|
Here are fixes that this release has, but have not been backported to
|
|
|
|
|
v1.6.2.X series.
|
|
|
|
|
|
