From: Junio C Hamano Date: Wed, 11 Mar 2009 21:37:26 +0000 (-0700) Subject: Merge branch 'maint' X-Git-Tag: v1.6.3-rc0~168 X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=64621462deb307ba784aac82b05010f464c67f8e;p=git.git Merge branch 'maint' * maint: Update draft release notes for 1.6.2.1 --- 64621462deb307ba784aac82b05010f464c67f8e diff --cc Documentation/RelNotes-1.6.3.txt index ee1fddb76,000000000..7f36b6c5c mode 100644,000000..100644 --- a/Documentation/RelNotes-1.6.3.txt +++ b/Documentation/RelNotes-1.6.3.txt @@@ -1,104 -1,0 +1,87 @@@ +GIT v1.6.3 Release Notes +======================== + +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. + + +Updates since v1.6.2 +-------------------- + +(subsystems) + +(performance) + +(usability, bells and whistles) + +* "--pretty=