1Git v2.0 Release Notes 2====================== 3 4Backward compatibility notes 5---------------------------- 6 7When "git push [$there]" does not say what to push, we have used the 8traditional "matching" semantics so far (all your branches were sent 9to the remote as long as there already are branches of the same name 10over there). In Git 2.0, the default is now the "simple" semantics, 11which pushes: 12 13 - only the current branch to the branch with the same name, and only 14 when the current branch is set to integrate with that remote 15 branch, if you are pushing to the same remote as you fetch from; or 16 17 - only the current branch to the branch with the same name, if you 18 are pushing to a remote that is not where you usually fetch from. 19 20You can use the configuration variable "push.default" to change 21this. If you are an old-timer who wants to keep using the 22"matching" semantics, you can set the variable to "matching", for 23example. Read the documentation for other possibilities. 24 25When "git add -u" and "git add -A" are run inside a subdirectory 26without specifying which paths to add on the command line, they 27operate on the entire tree for consistency with "git commit -a" and 28other commands (these commands used to operate only on the current 29subdirectory). Say "git add -u ." or "git add -A ." if you want to 30limit the operation to the current directory. 31 32"git add <path>" is the same as "git add -A <path>" now, so that 33"git add dir/" will notice paths you removed from the directory and 34record the removal. In older versions of Git, "git add <path>" used 35to ignore removals. You can say "git add --ignore-removal <path>" to 36add only added or modified paths in <path>, if you really want to. 37 38The "-q" option to "git diff-files", which does *NOT* mean "quiet", 39has been removed (it told Git to ignore deletion, which you can do 40with "git diff-files --diff-filter=d"). 41 42 43Updates since v1.9 series 44------------------------- 45 46Foreign interfaces, subsystems and ports. 47 48 49UI, Workflows & Features 50 51 * "git grep" learned to behave in a way similar to native grep when 52 "-h" (no header) and "-c" (count) options are given. 53 54 * transport-helper, fast-import and fast-export have been updated to 55 allow the ref mapping and ref deletion in a way similar to the 56 natively supported transports. 57 58 * The "simple" mode is the default for "git push". 59 60 * "git add -u" and "git add -A", when run without any pathspec, is a 61 tree-wide operation even when run inside a subdirectory of a 62 working tree. 63 64 * "git add <path> is the same as "git add -A <path>" now. 65 66 * "core.statinfo" configuration variable, which is a 67 never-advertised synonym to "core.checkstat", has been removed. 68 69 * The "-q" option to "git diff-files", which does *NOT* mean 70 "quiet", has been removed (it told Git to ignore deletion, which 71 you can do with "git diff-files --diff-filter=d"). 72 73 * Server operators can loosen the "tips of refs only" restriction for 74 the remote archive service with the uploadarchive.allowUnreachable 75 configuration option. 76 77 * The progress indicators from various time-consuming commands have 78 been marked for i18n/l10n. 79 80 * "git notes -C <blob>" diagnoses an attempt to use an object that 81 is not a blob as an error. 82 83 * "git config" learned to read from the standard input when "-" is 84 given as the value to its "--file" parameter (attempting an 85 operation to update the configuration in the standard input of 86 course is rejected). 87 88 * Trailing whitespaces in .gitignore files, unless they are quoted 89 for fnmatch(3), e.g. "path\ ", are warned and ignored. Strictly 90 speaking, this is a backward incompatible change, but very unlikely 91 to bite any sane user and adjusting should be obvious and easy. 92 93 * Many commands that create commits, e.g. "pull", "rebase", 94 learned to take the --gpg-sign option on the command line. 95 96 * "git commit" can be told to always GPG sign the resulting commit 97 by setting "commit.gpgsign" configuration variable to true (the 98 command line option --no-gpg-sign should override it). 99 100 * "git pull" can be told to only accept fast-forward by setting the 101 new "pull.ff" configuration. 102 103 * "git reset" learned "-N" option, which does not reset the index 104 fully for paths the index knows about but the tree-ish the command 105 resets to does not (these paths are kept as intend-to-add entries). 106 107 * Newly cloned submodule repositories by "git submodule update", 108 when the "checkout" update mode is used, will be on a local 109 branch instead of on a detached HEAD, just like submodules added 110 with "git submodule add". 111 112 113Performance, Internal Implementation, etc. 114 115 * We started using wildmatch() in place of fnmatch(3) a few releases 116 ago; complete the process and stop using fnmatch(3). 117 118 * Uses of curl's "multi" interface and "easy" interface do not mix 119 well when we attempt to reuse outgoing connections. Teach the RPC 120 over http code, used in the smart HTTP transport, not to use the 121 "easy" interface. 122 123 * The bitmap-index feature from JGit has been ported, which should 124 significantly improve performance when serving objects form a 125 repository that uses it. 126 127 * The way "git log --cc" shows a combined diff against multiple 128 parents have been optimized. 129 130 * The prefixcmp() and suffixcmp() functions are gone. Use 131 starts_with() and ends_with(), and also consider if skip_prefix() 132 suits your needs better when using the former. 133 134 135Also contains various documentation updates and code clean-ups. Many 136of them came from flurry of activities as GSoC candidate microproject 137exercises. 138 139 140Fixes since v1.9 series 141----------------------- 142 143Unless otherwise noted, all the fixes since v1.9 in the maintenance 144track are contained in this release (see the maintenance releases' 145notes for details). 146 147 * "git clean -d pathspec" did not use the given pathspec correctly 148 and ended up cleaning too much. 149 (merge 1f2e108 jk/clean-d-pathspec later to maint). 150 151 * "git difftool" misbehaved when the repository is bound to the 152 working tree with the ".git file" mechanism, where a textual file 153 ".git" tells us where it is. 154 (merge fcfec8b da/difftool-git-files later to maint). 155 156 * "git push" did not pay attention to branch.*.pushremote if it is 157 defined earlier than remote.pushdefault; the order of these two 158 variables in the configuration file should not matter, but it did 159 by mistake. 160 (merge 98b406f jk/remote-pushremote-config-reading later to maint). 161 162 * Codepaths that parse timestamps in commit objects have been 163 tightened. 164 (merge 3f419d4 jk/commit-dates-parsing-fix later to maint). 165 166 * "git diff --external-diff" incorrectly fed the submodule directory 167 in the working tree to the external diff driver when it knew it is 168 the same as one of the versions being compared. 169 (merge aba4727 tr/diff-submodule-no-reuse-worktree later to maint). 170 171 * "git reset" needs to refresh the index when working in a working 172 tree (it can also be used to match the index to the HEAD in an 173 otherwise bare repository), but it failed to set up the working 174 tree properly, causing GIT_WORK_TREE to be ignored. 175 (merge b7756d4 nd/reset-setup-worktree later to maint). 176 177 * "git check-attr" when working on a repository with a working tree 178 did not work well when the working tree was specified via the 179 --work-tree (and obviously with --git-dir) option. 180 (merge cdbf623 jc/check-attr-honor-working-tree later to maint). 181 182 * "merge-recursive" was broken in 1.7.7 era and stopped working in 183 an empty (temporary) working tree, when there are renames 184 involved. This has been corrected. 185 (merge 6e2068a bk/refresh-missing-ok-in-merge-recursive later to maint.) 186 187 * "git rev-parse" was loose in rejecting command line arguments 188 that do not make sense, e.g. "--default" without the required 189 value for that option. 190 (merge a43219f ds/rev-parse-required-args later to maint.) 191 192 * include.path variable (or any variable that expects a path that 193 can use ~username expansion) in the configuration file is not a 194 boolean, but the code failed to check it. 195 (merge 67beb60 jk/config-path-include-fix later to maint.) 196 197 * Commands that take pathspecs on the command line misbehaved when 198 the pathspec is given as an absolute pathname (which is a 199 practice not particularly encouraged) that points at a symbolic 200 link in the working tree. 201 (merge later 655ee9e mw/symlinks to maint.) 202 203 * "git diff --quiet -- pathspec1 pathspec2" sometimes did not return 204 correct status value. 205 (merge f34b205 nd/diff-quiet-stat-dirty later to maint.) 206 207 * Attempting to deepen a shallow repository by fetching over smart 208 HTTP transport failed in the protocol exchange, when no-done 209 extension was used. The fetching side waited for the list of 210 shallow boundary commits after the sending end stopped talking to 211 it. 212 (merge 0232852 nd/http-fetch-shallow-fix later to maint.) 213 214 * Allow "git cmd path/", when the 'path' is where a submodule is 215 bound to the top-level working tree, to match 'path', despite the 216 extra and unnecessary trailing slash (such a slash is often 217 given by command line completion). 218 (merge 2e70c01 nd/submodule-pathspec-ending-with-slash later to maint.)