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 25In a future release, the default of "git push" without further 26arguments might be changed. Currently, it will push all matching 27refspecs to the current remote. A configuration variable push.default 28has been introduced to select the default behaviour. To ease the 29transition, a big warning is issued if this is not configured and a 30git push without arguments is attempted. 31 32 33Updates since v1.6.2 34-------------------- 35 36(subsystems) 37 38(performance) 39 40* many uses of lstat(2) in the codepath for "git checkout" have been 41 optimized out. 42 43(usability, bells and whistles) 44 45* rsync:/path/to/repo can be used to run git over rsync for local 46 repositories. It may not be useful in practice; meant primarily for 47 testing. 48 49* (msysgit) progress output that is sent over the sideband protocol can 50 be handled appropriately in Windows console. 51 52* "--pretty=<style>" option to the log family of commands can now be 53 spelled as "--format=<style>". In addition, --format=%formatstring 54 is a short-hand for --pretty=tformat:%formatstring. 55 56* "--oneline" is a synonym for "--pretty=oneline --abbrev=commit". 57 58* If you realize that you botched the patch when you are editing hunks 59 with the 'edit' action in git-add -i/-p, you can abort the editor to 60 tell git not to apply it. 61 62* git-archive learned --output=<file> option. 63 64* git-bisect shows not just the number of remaining commits whose goodness 65 is unknown, but also shows the estimated number of remaining rounds. 66 67* You can give --date=<format> option to git-blame. 68 69* git-branch -r shows HEAD symref that points at a remote branch in 70 interest of each tracked remote repository. 71 72* git-config learned -e option to open an editor to edit the config file 73 directly. 74 75* git-clone runs post-checkout hook when run without --no-checkout. 76 77* git-format-patch can be told to use attachment with a new configuration, 78 format.attach. 79 80* git-format-patch can be told to produce deep or shallow message threads. 81 82* git-grep learned to highlight the found substrings in color. 83 84* git-imap-send learned to work around Thunderbird's inability to easily 85 disable format=flowed with a new configuration, imap.preformattedHTML. 86 87* git-rebase can be told to rebase the series even if your branch is a 88 descendant of the commit you are rebasing onto with --force-rebase 89 option. 90 91* git-rebase can be told to report diffstat with the --stat option. 92 93* Output from git-remote command has been vastly improved. 94 95* git-send-email learned --confirm option to review the Cc: list before 96 sending the messages out. 97 98(developers) 99 100* Test scripts can be run under valgrind. 101 102* Makefile learned 'coverage' option to run the test suites with 103 coverage tracking enabled. 104 105Fixes since v1.6.2 106------------------ 107 108All of the fixes in v1.6.2.X maintenance series are included in this 109release, unless otherwise noted. 110 111Here are fixes that this release has, but have not been backported to 112v1.6.2.X series. 113 114* git-gc spent excessive amount of time to decide if an object appears 115 in a locally existing pack (if needed, backport by merging 69e020a). 116 117--- 118exec >/var/tmp/1 119O=v1.6.2.1-213-g7d4e3a7 120echo O=$(git describe master) 121git shortlog --no-merges $O..master ^maint