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 25When the user does not tell "git push" what to push, it has always 26pushed matching refs. For some people it is unexpected, and a new 27configuration variable push.default has been introduced to allow 28changing a different default behaviour. To advertise the new feature, 29a big warning is issued if this is not configured and a git push without 30arguments is attempted. 31 32 33Updates since v1.6.2 34-------------------- 35 36(subsystems) 37 38* various git-svn updates. 39 40(performance) 41 42* many uses of lstat(2) in the codepath for "git checkout" have been 43 optimized out. 44 45* pruning reflog entries that are unreachable from the tip of the ref 46 during "git reflog prune" (hence "git gc") was very inefficient. 47 48(usability, bells and whistles) 49 50* Boolean configuration variable yes/no can be written as on/off. 51 52* rsync:/path/to/repo can be used to run git over rsync for local 53 repositories. It may not be useful in practice; meant primarily for 54 testing. 55 56* http transport learned to prompt and use password when fetching from or 57 pushing to http://user@host.xz/ URL. 58 59* (msysgit) progress output that is sent over the sideband protocol can 60 be handled appropriately in Windows console. 61 62* "--pretty=<style>" option to the log family of commands can now be 63 spelled as "--format=<style>". In addition, --format=%formatstring 64 is a short-hand for --pretty=tformat:%formatstring. 65 66* "--oneline" is a synonym for "--pretty=oneline --abbrev-commit". 67 68* "--graph" to the "git log" family can draw the commit ancestry graph 69 in colors. 70 71* If you realize that you botched the patch when you are editing hunks 72 with the 'edit' action in git-add -i/-p, you can abort the editor to 73 tell git not to apply it. 74 75* The number of commits shown in "you are ahead/behind your upstream" 76 messages given by "git checkout" and "git status" used to count merge 77 commits; now it doesn't. 78 79* @{-1} is a new way to refer to the last branch you were on introduced in 80 1.6.2, but the initial implementation did not teach this to a few 81 commands. Now the syntax works with "branch -m @{-1} newname". 82 83* "git-add -p" now supports "q"uit action. 84 85* git-archive learned --output=<file> option. 86 87* git-archive takes attributes from the tree being archived; strictly 88 speaking, this is an incompatible behaviour change, but is a good one. 89 Use --worktree-attributes option to allow it to read attributes from 90 the work tree as before (deprecated git-tar tree command always reads 91 attributes from the work tree). 92 93* git-bisect shows not just the number of remaining commits whose goodness 94 is unknown, but also shows the estimated number of remaining rounds. 95 96* You can give --date=<format> option to git-blame. 97 98* "git-branch -r" shows HEAD symref that points at a remote branch in 99 interest of each tracked remote repository. 100 101* "git-branch -v -v" is a new way to get list of names for branches and the 102 "upstream" branch for them. 103 104* git-config learned -e option to open an editor to edit the config file 105 directly. 106 107* git-clone runs post-checkout hook when run without --no-checkout. 108 109* git-difftool is now part of the officially supported command, primarily 110 maintained by David Aguilar. 111 112* git-fast-export choked when seeing a tag that does not point at commit. 113 114* git-for-each-ref learned a new "upstream" token. 115 116* git-format-patch can be told to use attachment with a new configuration, 117 format.attach. 118 119* git-format-patch can be told to produce deep or shallow message threads. 120 121* git-format-patch can be told to always add sign-off with a configuration 122 variable. 123 124* git-format-patch learned format.headers configuration to add extra 125 header fields to the output. This behaviour is similar to the existing 126 --add-header=<header> option of the command. 127 128* git-format-patch gives human readable names to the attached files, when 129 told to send patches as attachments. 130 131* git-grep learned to highlight the found substrings in color. 132 133* git-imap-send learned to work around Thunderbird's inability to easily 134 disable format=flowed with a new configuration, imap.preformattedHTML. 135 136* git-rebase can be told to rebase the series even if your branch is a 137 descendant of the commit you are rebasing onto with --force-rebase 138 option. 139 140* git-rebase can be told to report diffstat with the --stat option. 141 142* Output from git-remote command has been vastly improved. 143 144* "git remote update --prune $remote" updates from the named remote and 145 then prunes stale tracking branches. 146 147* git-send-email learned --confirm option to review the Cc: list before 148 sending the messages out. 149 150(developers) 151 152* Test scripts can be run under valgrind. 153 154* Test scripts can be run with installed git. 155 156* Makefile learned 'coverage' option to run the test suites with 157 coverage tracking enabled. 158 159* Building the manpages with docbook-xsl between 1.69.1 and 1.71.1 now 160 requires setting DOCBOOK_SUPPRESS_SP to work around a docbook-xsl bug. 161 This workaround used to be enabled by default, but causes problems 162 with newer versions of docbook-xsl. In addition, there are a few more 163 knobs you can tweak to work around issues with various versions of the 164 docbook-xsl package. See comments in Documentation/Makefile for details. 165 166Fixes since v1.6.2 167------------------ 168 169All of the fixes in v1.6.2.X maintenance series are included in this 170release, unless otherwise noted. 171 172Here are fixes that this release has, but have not been backported to 173v1.6.2.X series. 174 175* "git-apply" rejected a patch that swaps two files (i.e. renames A to B 176 and B to A at the same time). May need to be backported by cherry 177 picking d8c81df and then 7fac0ee). 178 179* The initial checkout did not read the attributes from the .gitattribute 180 file that is being checked out. 181 182* git-gc spent excessive amount of time to decide if an object appears 183 in a locally existing pack (if needed, backport by merging 69e020a). 184 185--- 186exec >/var/tmp/1 187O=v1.6.3-rc0-74-g9824a38 188echo O=$(git describe master) 189git shortlog --no-merges $O..master ^maint