From: Junio C Hamano Date: Sun, 15 Mar 2009 20:10:10 +0000 (-0700) Subject: Sync with GIT 1.6.2.1 X-Git-Tag: v1.6.3-rc0~160 X-Git-Url: https://git.tokkee.org/?a=commitdiff_plain;h=de7697808fd8b552479a60fa3b98440d541b42de;p=git.git Sync with GIT 1.6.2.1 --- de7697808fd8b552479a60fa3b98440d541b42de diff --cc Documentation/RelNotes-1.6.3.txt index f519739ab,000000000..679ad28b9 mode 100644,000000..100644 --- a/Documentation/RelNotes-1.6.3.txt +++ b/Documentation/RelNotes-1.6.3.txt @@@ -1,104 -1,0 +1,104 @@@ +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=