1Git v1.7.0 Release Notes 2======================== 3 4Notes on behaviour change 5------------------------- 6 7 * "git push" into a branch that is currently checked out (i.e. pointed by 8 HEAD in a repository that is not bare) is refused by default. 9 10 Similarly, "git push $there :$killed" to delete the branch $killed 11 in a remote repository $there, when $killed branch is the current 12 branch pointed at by its HEAD, will be refused by default. 13 14 Setting the configuration variables receive.denyCurrentBranch and 15 receive.denyDeleteCurrent to 'ignore' in the receiving repository 16 can be used to override these safety features. 17 18 * "git send-email" does not make deep threads by default when sending a 19 patch series with more than two messages. All messages will be sent 20 as a reply to the first message, i.e. cover letter. 21 22 It has been possible to configure send-email to send "shallow thread" 23 by setting sendemail.chainreplyto configuration variable to false. The 24 only thing this release does is to change the default when you haven't 25 configured that variable. 26 27 * "git status" is not "git commit --dry-run" anymore. This change does 28 not affect you if you run the command without pathspec. 29 30 * "git diff" traditionally treated various "ignore whitespace" options 31 only as a way to filter the patch output. "git diff --exit-code -b" 32 exited with non-zero status even if all changes were about changing the 33 ammount of whitespace and nothing else. and "git diff -b" showed the 34 "diff --git" header line for such a change without patch text. 35 36 In this release, the "ignore whitespaces" options affect the semantics 37 of the diff operation. A change that does not affect anything but 38 whitespaces is reported with zero exit status when run with 39 --exit-code, and there is no "diff --git" header for such a change. 40 41 42Updates since v1.6.6 43-------------------- 44 45(subsystems) 46 47(portability) 48 49(performance) 50 51(usability, bells and whistles) 52 53 * "git commit --date='<date>'" can be used to override the author date 54 just like "git commit --author='<name> <email>'" can be used to 55 override the author identity. 56 57 * "git status" learned "-s(hort)" output format. 58 59 60Fixes since v1.6.6 61------------------ 62 63All of the fixes in v1.6.6.X maintenance series are included in this 64release, unless otherwise noted. 65 66-- 67exec >/var/tmp/1 68O=v1.6.6-101-gf012d27 69echo O=$(git describe master) 70git shortlog --no-merges $O..master ^maint