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* git-branch -r shows HEAD symref that points at a remote branch in 51 interest of each tracked remote repository. 52 53* git-config learned -e option to open an editor to edit the config file 54 directly. 55 56* git-format-patch can be told to use attachment with a new configuration, 57 format.attach. 58 59* git-imap-send learned to work around Thunderbird's inability to easily 60 disable format=flowed with a new configuration, imap.preformattedHTML. 61 62* git-rebase can be told to rebase the series even if your branch is a 63 descendant of the commit you are rebasing onto with --force-rebase 64 option. 65 66* git-send-email learned --confirm option to review the Cc: list before 67 sending the messages out. 68 69(developers) 70 71* Test scripts can be run under valgrind. 72 73 74Fixes since v1.6.2 75------------------ 76 77All of the fixes in v1.6.2.X maintenance series are included in this 78release, unless otherwise noted. 79 80Here are fixes that this release has, but have not been backported to 81v1.6.2.X series. 82 83* .gitignore learned to handle backslash as a quoting mechanism for 84 comment introduction character "#" (backport by merging dd482ee if 85 needed). 86 87* timestamp output in --date=relative mode used to display timestamps that 88 are long time ago in the default mode; it now uses "N years M months 89 ago", and "N years ago" (backport by picking 10edf37 if needed). 90 91* git-add -i/-p now works with non-ASCII pathnames (backport by picking 92 8851f48 if needed). 93 94* "git hash-object -w" did not read from the configuration file from the 95 correct .git directory (backport by merging 272459a if needed). 96 97* git-send-email learned to correctly handle multiple Cc: addresses 98 (backport by merging afe756c if needed). 99 100--- 101exec >/var/tmp/1 102O=v1.6.2-77-g8cc3fe4 103echo O=$(git describe master) 104git shortlog --no-merges $O..master ^maint