1Git v1.7.0 Release Notes 2======================== 3 4Notes on behaviour change 5------------------------- 6 7 * "git push" into a branch that is currently checked out (i.e. pointed by 8 HEAD in a repository that is not bare) is refused by default. 9 10 Similarly, "git push $there :$killed" to delete the branch $killed 11 in a remote repository $there, when $killed branch is the current 12 branch pointed at by its HEAD, will be refused by default. 13 14 Setting the configuration variables receive.denyCurrentBranch and 15 receive.denyDeleteCurrent to 'ignore' in the receiving repository 16 can be used to override these safety features. 17 18 * "git send-email" does not make deep threads by default when sending a 19 patch series with more than two messages. All messages will be sent 20 as a reply to the first message, i.e. cover letter. 21 22 It has been possible to configure send-email to send "shallow thread" 23 by setting sendemail.chainreplyto configuration variable to false. The 24 only thing this release does is to change the default when you haven't 25 configured that variable. 26 27 * "git status" is not "git commit --dry-run" anymore. This change does 28 not affect you if you run the command without argument. 29 30 * "git diff" traditionally treated various "ignore whitespace" options 31 only as a way to filter the patch output. "git diff --exit-code -b" 32 exited with non-zero status even if all changes were about changing the 33 ammount of whitespace and nothing else. and "git diff -b" showed the 34 "diff --git" header line for such a change without patch text. 35 36 In this release, the "ignore whitespaces" options affect the semantics 37 of the diff operation. A change that does not affect anything but 38 whitespaces is reported with zero exit status when run with 39 --exit-code, and there is no "diff --git" header for such a change. 40 41 * External diff and textconv helpers are now executed using the shell. 42 This makes them consistent with other programs executed by git, and 43 allows you to pass command-line parameters to the helpers. Any helper 44 paths containing spaces or other metacharacters now need to be 45 shell-quoted. The affected helpers are GIT_EXTERNAL_DIFF in the 46 environment, and diff.*.command and diff.*.textconv in the config 47 file. 48 49 * The --max-pack-size argument to 'git repack', 'git pack-objects', and 50 'git fast-import' was assuming the provided size to be expressed in MiB, 51 unlike the corresponding config variable and other similar options accepting 52 a size value. It is now expecting a size expressed in bytes, with a possible 53 unit suffix of 'k', 'm', or 'g'. 54 55Updates since v1.6.6 56-------------------- 57 58(subsystems) 59 60 * "git fast-import" updates; adds "option" and "feature" to detect the 61 mismatch between fast-import and the frontends that produce the input 62 stream. 63 64 * "git svn" support of subversion "merge tickets" and miscellaneous fixes. 65 66 * "gitk" and "git gui" translation updates. 67 68 * "gitweb" updates (code clean-up, load checking etc.) 69 70(portability) 71 72 * Some more MSVC portability patches for msysgit port. 73 74 * Minimum Pthreads emulation for msysgit port. 75 76(performance) 77 78 * More performance improvement patches for msysgit port. 79 80(usability, bells and whistles) 81 82 * More commands learned "--quiet" and "--[no-]progress" options. 83 84 * Various commands given by the end user (e.g. diff.type.textconv, 85 and GIT_EDITOR) can be specified with command line arguments. E.g. it 86 is now possible to say "[diff "utf8doc"] textconv = nkf -w". 87 88 * "sparse checkout" feature allows only part of the work tree to be 89 checked out. 90 91 * HTTP transfer can use authentication scheme other than basic 92 (i.e./e.g. digest). 93 94 * Switching from a version of superproject that used to have a submodule 95 to another version of superproject that no longer has it did not remove 96 the submodule directory when it should (namely, when you are not 97 interested in the submodule at all and didn't clone/checkout). 98 99 * A new attribute conflict-marker-size can be used to change the size of 100 the conflict markers from the default 7; this is useful when tracked 101 contents (e.g. git-merge documentation) have strings that resemble the 102 conflict markers. 103 104 * A new syntax "<branch>@{upstream}" can be used on the command line to 105 substitute the name of the "upstream" of the branch. Missing branch 106 defaults to the current branch, so "git fetch && git merge @{upstream}" 107 will be equivalent to "git pull". 108 109 * "git branch --set-upstream" can be used to update the (surprise!) upstream 110 i.e. where the branch is supposed to pull and merge from (or rebase onto). 111 112 * "git checkout A...B" is a way to detach HEAD at the merge base between 113 A and B. 114 115 * "git checkout -m path" to reset the work tree file back into the 116 conflicted state works even when you already ran "git add path" and 117 resolved the conflicts. 118 119 * "git commit --date='<date>'" can be used to override the author date 120 just like "git commit --author='<name> <email>'" can be used to 121 override the author identity. 122 123 * "git commit --no-status" can be used to omit the listing of the index 124 and the work tree status in the editor used to prepare the log message. 125 126 * "git commit" warns a bit more aggressively until you configure user.email, 127 whose default value almost always is not (and fundamentally cannot be) 128 what you want. 129 130 * "git difftool" has been extended to make it easier to integrate it 131 with gitk. 132 133 * "git fetch --all" can now be used in place of "git remote update". 134 135 * "git grep" does not rely on external grep anymore. It can use more than 136 one threads to accelerate the operation. 137 138 * "git grep" learned "--quiet" option. 139 140 * "git log" and friends learned "--glob=heads/*" syntax that is a more 141 flexible way to complement "--branches/--tags/--remotes". 142 143 * "git merge" learned to pass options specific to strategy-backends. E.g. 144 145 - "git merge -Xsubtree=path/to/directory" can be used to tell the subtree 146 strategy how much to shift the trees explicitly. 147 148 - "git merge -Xtheirs" can be used to auto-merge as much as possible, 149 while discarding your own changes and taking merged version in 150 conflicted regions. 151 152 * "git push" learned "git push origin --delete branch", a syntactic sugar 153 for "git push origin :branch". 154 155 * "git push" learned "git push --set-upstream origin forker:forkee" that 156 lets you configure your "forker" branch to later pull from "forkee" 157 branch at "origin". 158 159 * "git rebase --onto A...B" means the history is replayed on top of the 160 merge base between A and B. 161 162 * "git rebase -i" learned new action "fixup", that squashes the change 163 but does not affect existing log message. 164 165 * "git rebase -i" also learned --autosquash option, that is useful 166 together with the new "fixup" action. 167 168 * "git remote" learned set-url subcommand, to update (surprise!) url 169 for an existing remote nickname. 170 171 * "git rerere" learned "forget path" subcommand. Together with "git 172 checkout -m path" it will be useful when you recorded a wrong 173 resolution. 174 175 * Use of "git reset --merge" has become easier when resetting away a 176 conflicted mess left in the work tree. 177 178 * "git rerere" had rerere.autoupdate configuration but there was no way 179 to countermand it from the command line; --no-rerere-autoupdate option 180 given to "merge", "revert", etc. fixes this. 181 182 * "git status" learned "-s(hort)" output format. 183 184(developers) 185 186 * The infrastructure to build foreign SCM interface has been updated. 187 188 * Many more commands are now built-in. 189 190 * THREADED_DELTA_SEARCH is no more. If you build with threads, delta 191 compression will always take advantage of it. 192 193Fixes since v1.6.6 194------------------ 195 196All of the fixes in v1.6.6.X maintenance series are included in this 197release, unless otherwise noted. 198 199 * "git branch -d branch" used to refuse deleting the branch even when 200 the branch is fully merged to its upstream branch if it is not merged 201 to the current branch. It now deletes it in such a case. 202 203 * When using "git status" or asking "git diff" to compare the work tree 204 with something, they used to consider that a checked-out submodule with 205 uncommitted changes is not modified; this could cause people to forget 206 committing these changes in the submodule before committing in the 207 superproject. They now consider such a change as a modification and 208 "git diff" will append a "-dirty" to the work tree side when generating 209 patch output or when used with the --submodule option.