|
| 1 | +GIT v1.6.5 Release Notes |
| 2 | +======================== |
| 3 | + |
| 4 | +In git 1.7.0, which is planned to be the release after 1.6.5, "git push" |
| 5 | +into a branch that is currently checked out will be refused by default. |
| 6 | + |
| 7 | +You can choose what should happen upon such a push by setting the |
| 8 | +configuration variable receive.denyCurrentBranch in the receiving |
| 9 | +repository. |
| 10 | + |
| 11 | +Also, "git push $there :$killed" to delete the branch $killed in a remote |
| 12 | +repository $there, when $killed branch is the current branch pointed at by |
| 13 | +its HEAD, will be refused by default. |
| 14 | + |
| 15 | +You can choose what should happen upon such a push by setting the |
| 16 | +configuration variable receive.denyDeleteCurrent in the receiving |
| 17 | +repository. |
| 18 | + |
| 19 | +To ease the transition plan, the receiving repository of such a |
| 20 | +push running this release will issue a big warning when the |
| 21 | +configuration variable is missing. Please refer to: |
| 22 | + |
| 23 | + http://git.or.cz/gitwiki/GitFaq#non-bare |
| 24 | + http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007 |
| 25 | + |
| 26 | +for more details on the reason why this change is needed and the |
| 27 | +transition plan. |
| 28 | + |
| 29 | +Updates since v1.6.4 |
| 30 | +-------------------- |
| 31 | + |
| 32 | +(subsystems) |
| 33 | + |
| 34 | +(portability) |
| 35 | + |
| 36 | +(performance) |
| 37 | + |
| 38 | +(usability, bells and whistles) |
| 39 | + |
| 40 | +(developers) |
| 41 | + |
| 42 | +Fixes since v1.6.4 |
| 43 | +------------------ |
| 44 | + |
| 45 | +# All of the fixes in v1.6.4.X maintenance series are included in this |
| 46 | +# release, unless otherwise noted. |
| 47 | + |
| 48 | +# Here are fixes that this release has, but have not been backported to |
| 49 | +# v1.6.4.X series. |
| 50 | + |
| 51 | + |
0 commit comments