1Git v1.6.6 Release Notes 2======================== 3 4Notes on behaviour change 5------------------------- 6 7 * In this release, "git fsck" defaults to "git fsck --full" and 8 checks packfiles, and because of this it will take much longer to 9 complete than before. If you prefer a quicker check only on loose 10 objects (the old default), you can say "git fsck --no-full". This 11 has been supported by 1.5.4 and newer versions of git, so it is 12 safe to write it in your script even if you use slightly older git 13 on some of your machines. 14 15Preparing yourselves for compatibility issues in 1.7.0 16------------------------------------------------------ 17 18In git 1.7.0, which is planned to be the release after 1.6.6, there will 19be a handful of behaviour changes that will break backward compatibility. 20 21These changes were discussed long time ago and existing behaviours have 22been identified as more problematic to the userbase than keeping them for 23the sake of backward compatibility. 24 25When necessary, transition strategy for existing users has been designed 26not to force them running around setting configuration variables and 27updating their scripts in order to keep the traditional behaviour on the 28day their sysadmin decides to install the new version of git. When we 29switched from "git-foo" to "git foo" in 1.6.0, even though the change had 30been advertised and the transition guide had been provided for a very long 31time, the users procrastinated during the entire transtion period, and 32ended up panicking on the day their sysadmins updated their git. 33 34For changes decided to be in 1.7.0, we have been much louder to strongly 35discourage such procrastination. If you have been using recent versions 36of git, you would have already seen warnings issued when you exercised 37features whose behaviour will change, with the instruction on how to keep 38the existing behaviour if you choose to. You hopefully should be well 39prepared already. 40 41Of course, we have also given "this and that will change in 1.7.0; prepare 42yourselves" warnings in the release notes and announcement messages. 43Let's see how well users will fare this time. 44 45 * "git push" into a branch that is currently checked out (i.e. pointed by 46 HEAD in a repository that is not bare) will be refused by default. 47 48 Similarly, "git push $there :$killed" to delete the branch $killed 49 in a remote repository $there, when $killed branch is the current 50 branch pointed at by its HEAD, will be refused by default. 51 52 Setting the configuration variables receive.denyCurrentBranch and 53 receive.denyDeleteCurrent to 'ignore' in the receiving repository 54 can be used to override these safety features. Versions of git 55 since 1.6.2 have issued a loud warning when you tried to do them 56 without setting the configuration, so repositories of people who 57 still need to be able to perform such a push should already been 58 future proofed. 59 60 Please refer to: 61 62 http://git.or.cz/gitwiki/GitFaq#non-bare 63 http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007 64 65 for more details on the reason why this change is needed and the 66 transition process that already took place so far. 67 68 * "git send-email" will not make deep threads by default when sending a 69 patch series with more than two messages. All messages will be sent as 70 a reply to the first message, i.e. cover letter. It has been possible 71 to configure send-email to do this by setting sendemail.chainreplyto 72 configuration variable to false. The only thing the new release will 73 do is to change the default when you haven't configured that variable. 74 75 * "git status" will not be "git commit --dry-run". This change does not 76 affect you if you run the command without pathspec. 77 78 Nobody sane found the current behaviour of "git status Makefile" useful 79 nor meaningful, and it confused users. "git commit --dry-run" has been 80 provided as a way to get the current behaviour of this command since 81 1.6.5. 82 83 * "git diff" traditionally treated various "ignore whitespace" options 84 only as a way to filter the patch output. "git diff --exit-code -b" 85 exited with non-zero status even if all changes were about changing the 86 ammount of whitespace and nothing else. and "git diff -b" showed the 87 "diff --git" header line for such a change without patch text. 88 89 In 1.7.0, the "ignore whitespaces" will affect the semantics of the 90 diff operation itself. A change that does not affect anything but 91 whitespaces will be reported with zero exit status when run with 92 --exit-code, and there will not be "diff --git" header for such a 93 change. 94 95 96Updates since v1.6.5 97-------------------- 98 99(subsystems) 100 101 * various git-gui updates including new translations, wm states, etc. 102 103 * git-svn updates. 104 105 * "git fetch" over http learned a new mode that is different from the 106 traditional "dumb commit walker". 107 108(portability) 109 110 * imap-send can be built on mingw port. 111 112(performance) 113 114 * "git diff -B" has smaller memory footprint. 115 116(usability, bells and whistles) 117 118 * The object replace mechanism can be bypassed with --no-replace-objects 119 global option given to the "git" program. 120 121 * In configuration files, a few variables that name paths can begin with ~/ 122 and ~username/ and they are expanded as expected. 123 124 * "git subcmd -h" now shows short usage help for many more subcommands. 125 126 * "git bisect reset" can reset to an arbitrary commit. 127 128 * "git checkout frotz" when there is no local branch "frotz" but there 129 is only one remote tracking branch "frotz" is taken as a request to 130 start the named branch at the corresponding remote tracking branch. 131 132 * "git describe" can be told to add "-dirty" suffix with "--dirty" option. 133 134 * "git diff" learned --submodule option to show a list of one-line logs 135 instead of differences between the commit object names. 136 137 * "git fetch" learned --all and --multiple options, to run fetch from 138 many repositories, and --prune option to remove remote tracking 139 branches that went stale. These make "git remote update" and "git 140 remote prune" less necessary (there is no plan to remove "remote 141 update" nor "remote prune", though). 142 143 * "git fsck" by default checks the packfiles (i.e. "--full" is the 144 default); you can turn it off with "git fsck --no-full". 145 146 * "git grep" can use -F (fixed strings) and -i (ignore case) together. 147 148 * import-tars contributed fast-import frontend learned more types of 149 compressed tarballs. 150 151 * "git instaweb" knows how to talk with mod_cgid to apache2. 152 153 * "git log --decorate" shows the location of HEAD as well. 154 155 * "git log" and "git rev-list" learned to take revs and pathspecs from 156 the standard input with the new "--stdin" option. 157 158 * "--pretty=format" option to "log" family of commands learned: 159 160 . to wrap text with the "%w()" specifier. 161 . to show reflog information with "%g[sdD]" specifier. 162 163 * "git notes" command to annotate existing commits. 164 165 * "git merge" (and "git pull") learned --ff-only option to make it fail 166 if the merge does not result in a fast-forward. 167 168 * "git mergetool" learned to use p4merge. 169 170 * "git rebase -i" learned "reword" that acts like "edit" but immediately 171 starts an editor to tweak the log message without returning control to 172 the shell, which is done by "edit" to give an opportunity to tweak the 173 contents. 174 175 * In "git submodule add <repository> <path>", <path> is now optional and 176 inferred from <repository> the same way "git clone <repository>" does. 177 178 * "git svn" learned to read SVN 1.5+ and SVK merge tickets. 179 180 * Author names shown in gitweb output are links to search commits by the 181 author. 182 183 184(developers) 185 186Fixes since v1.6.5 187------------------ 188 189All of the fixes in v1.6.5.X maintenance series are included in this 190release, unless otherwise noted. 191 192--- 193exec >/var/tmp/1 194echo O=$(git describe master) 195O=v1.6.6-rc0-62-g7fc9d15 196git shortlog --no-merges $O..master --not maint