1GIT v1.6.6 Release Notes 2======================== 3 4In this release, "git fsck" defaults to "git fsck --full" and checks 5packfiles, and because of this it will take much longer to complete 6than before. If you prefer a quicker check only on loose objects (the 7old default), you can say "git fsck --no-full". This has been 8supported by 1.5.4 and newer versions of git, so it is safe to write 9it in your script even if you use slightly older git on some of your 10machines. 11 12In git 1.7.0, which is planned to be the release after 1.6.6, "git 13push" into a branch that is currently checked out will be refused by 14default. 15 16You can choose what should happen upon such a push by setting the 17configuration variable receive.denyCurrentBranch in the receiving 18repository. 19 20Also, "git push $there :$killed" to delete the branch $killed in a remote 21repository $there, when $killed branch is the current branch pointed at by 22its HEAD, will be refused by default. 23 24You can choose what should happen upon such a push by setting the 25configuration variable receive.denyDeleteCurrent in the receiving 26repository. 27 28To ease the transition plan, the receiving repository of such a 29push running this release will issue a big warning when the 30configuration variable is missing. Please refer to: 31 32 http://git.or.cz/gitwiki/GitFaq#non-bare 33 http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007 34 35for more details on the reason why this change is needed and the 36transition plan. 37 38Updates since v1.6.5 39-------------------- 40 41(subsystems) 42 43(portability) 44 45(performance) 46 47(usability, bells and whistles) 48 49 * "git fsck" by default checks the packfiles (i.e. "--full" is the 50 default); you can turn it off with "git fsck --no-full". 51 52 * "git log --decorate" shows the location of HEAD as well. 53 54(developers) 55 56Fixes since v1.6.5 57------------------ 58 59All of the fixes in v1.6.5.X maintenance series are included in this 60release, unless otherwise noted. 61 62 * "git apply" and "git diff" (including patch output from "git log -p") 63 now flags trailing blank lines as whitespace errors correctly (only 64 "apply --whitespace=fix" stripped them but "apply --whitespace=warn" 65 did not even warn). 66 67 * Two whitespace error classes, 'blank-at-eof' and 'blank-at-eol', have 68 been introduced (settable by core.whitespace configuration variable and 69 whitespace attribute). The 'trailing-space' whitespace error class has 70 become a short-hand to cover both of these and there is no behaviour 71 change for existing set-ups.