1GIT v1.6.3 Release Notes 2======================== 3 4With the next major release, "git push" into a branch that is 5currently checked out will be refused by default. You can choose 6what should happen upon such a push by setting the configuration 7variable receive.denyCurrentBranch in the receiving repository. 8 9To ease the transition plan, the receiving repository of such a 10push running this release will issue a big warning when the 11configuration variable is missing. Please refer to: 12 13 http://git.or.cz/gitwiki/GitFaq#non-bare 14 http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007 15 16for more details on the reason why this change is needed and the 17transition plan. 18 19For a similar reason, "git push $there :$killed" to delete the branch 20$killed in a remote repository $there, if $killed branch is the current 21branch pointed at by its HEAD, gets a large warning. You can choose what 22should happen upon such a push by setting the configuration variable 23receive.denyDeleteCurrent in the receiving repository. 24 25 26Updates since v1.6.2 27-------------------- 28 29(subsystems) 30 31(performance) 32 33(usability, bells and whistles) 34 35* "--pretty=<style>" option to the log family of commands can now be 36 spelled as "--format=<style>". In addition, --format=%formatstring 37 is a short-hand for --pretty=tformat:%formatstring. 38 39* "--oneline" is a synonym for "--pretty=oneline --abbrev=commit". 40 41* If you realize that you botched the patch when you are editing hunks 42 with the 'edit' action in git-add -i/-p, you can abort the editor to 43 tell git not to apply it. 44 45* git-archive learned --output=<file> option. 46 47* git-bisect shows not just the number of remaining commits whose goodness 48 is unknown, but also shows the estimated number of remaining rounds. 49 50* You can give --date=<format> option to git-blame. 51 52* git-branch -r shows HEAD symref that points at a remote branch in 53 interest of each tracked remote repository. 54 55* git-config learned -e option to open an editor to edit the config file 56 directly. 57 58* git-clone runs post-checkout hook when run without --no-checkout. 59 60* git-format-patch can be told to use attachment with a new configuration, 61 format.attach. 62 63* git-format-patch can be told to produce deep or shallow message threads. 64 65* git-imap-send learned to work around Thunderbird's inability to easily 66 disable format=flowed with a new configuration, imap.preformattedHTML. 67 68* git-rebase can be told to rebase the series even if your branch is a 69 descendant of the commit you are rebasing onto with --force-rebase 70 option. 71 72* git-rebase can be told to report diffstat with the --stat option. 73 74* git-send-email learned --confirm option to review the Cc: list before 75 sending the messages out. 76 77(developers) 78 79* Test scripts can be run under valgrind. 80 81* Makefile learned 'coverage' option to run the test suites with 82 coverage tracking enabled. 83 84Fixes since v1.6.2 85------------------ 86 87All of the fixes in v1.6.2.X maintenance series are included in this 88release, unless otherwise noted. 89 90Here are fixes that this release has, but have not been backported to 91v1.6.2.X series. 92 93* 'git-submodule add' did not tolerate extra slashes and ./ in the 94 path it accepted from the command line; it now is more lenient 95 (if needed, backport by merging db75ada). 96 97* git-gc spent excessive amount of time to decide if an object appears 98 in a locally existing pack (if needed, backport by merging 69e020a). 99 100--- 101exec >/var/tmp/1 102O=v1.6.2.1-135-g7d65c21 103echo O=$(git describe master) 104git shortlog --no-merges $O..master ^maint