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