4 Backward compatibility notes
5 ----------------------------
7 "git submodule foreach $cmd $args" used to treat "$cmd $args" the same
8 way "ssh" did, concatenating them into a single string and letting the
9 shell unquote. Careless users who forget to sufficiently quote $args
10 gets their argument split at $IFS whitespaces by the shell, and got
11 unexpected results due to this. Starting from this release, the
12 command line is passed directly to the shell, if it has an argument.
14 Read-only support for experimental loose-object format, in which users
15 could optionally choose to write in their loose objects for a short
16 while between v1.4.3 to v1.5.3 era, has been dropped.
18 The meanings of "--tags" option to "git fetch" has changed; the
19 command fetches tags _in addition to_ what are fetched by the same
20 command line without the option.
22 The way "git push $there $what" interprets $what part given on the
23 command line, when it does not have a colon that explicitly tells us
24 what ref at the $there repository is to be updated, has been enhanced.
26 A handful of ancient commands that have long been deprecated are
27 finally gone (repo-config, tar-tree, lost-found, and peek-remote).
30 Backward compatibility notes (for Git 2.0)
31 ------------------------------------------
33 When "git push [$there]" does not say what to push, we have used the
34 traditional "matching" semantics so far (all your branches were sent
35 to the remote as long as there already are branches of the same name
36 over there). In Git 2.0, the default will change to the "simple"
37 semantics, which pushes:
39 - only the current branch to the branch with the same name, and only
40 when the current branch is set to integrate with that remote
41 branch, if you are pushing to the same remote as you fetch from; or
43 - only the current branch to the branch with the same name, if you
44 are pushing to a remote that is not where you usually fetch from.
46 Use the user preference configuration variable "push.default" to
47 change this. If you are an old-timer who is used to the "matching"
48 semantics, you can set the variable to "matching" to keep the
49 traditional behaviour. If you want to live in the future early, you
50 can set it to "simple" today without waiting for Git 2.0.
52 When "git add -u" (and "git add -A") is run inside a subdirectory and
53 does not specify which paths to add on the command line, it
54 will operate on the entire tree in Git 2.0 for consistency
55 with "git commit -a" and other commands. There will be no
56 mechanism to make plain "git add -u" behave like "git add -u .".
57 Current users of "git add -u" (without a pathspec) should start
58 training their fingers to explicitly say "git add -u ."
59 before Git 2.0 comes. A warning is issued when these commands are
60 run without a pathspec and when you have local changes outside the
61 current directory, because the behaviour in Git 2.0 will be different
62 from today's version in such a situation.
64 In Git 2.0, "git add <path>" will behave as "git add -A <path>", so
65 that "git add dir/" will notice paths you removed from the directory
66 and record the removal. Versions before Git 2.0, including this
67 release, will keep ignoring removals, but the users who rely on this
68 behaviour are encouraged to start using "git add --ignore-removal <path>"
69 now before 2.0 is released.
71 The default prefix for "git svn" will change in Git 2.0. For a long
72 time, "git svn" created its remote-tracking branches directly under
73 refs/remotes, but it will place them under refs/remotes/origin/ unless
74 it is told otherwise with its --prefix option.
80 Foreign interfaces, subsystems and ports.
82 * The HTTP transport, when talking GSS-Negotiate, uses "100
83 Continue" response to avoid having to rewind and resend a large
84 payload, which may not be always doable.
86 * Various bugfixes to remote-bzr and remote-hg (in contrib/).
88 * The build procedure is aware of MirBSD now.
90 * Various "git p4", "git svn" and "gitk" updates.
93 UI, Workflows & Features
95 * Fetching from a shallowly-cloned repository used to be forbidden,
96 primarily because the codepaths involved were not carefully vetted
97 and we did not bother supporting such usage. This release attempts
98 to allow object transfer out of a shallowly-cloned repository in a
99 more controlled way (i.e. the receiver become a shallow repository
100 with a truncated history).
102 * Just like we give a reasonable default for "less" via the LESS
103 environment variable, we now specify a reasonable default for "lv"
104 via the "LV" environment variable when spawning the pager.
106 * Two-level configuration variable names in "branch.*" and "remote.*"
107 hierarchies, whose variables are predominantly three-level, were
108 not completed by hitting a <TAB> in bash and zsh completions.
110 * Fetching 'frotz' branch with "git fetch", while 'frotz/nitfol'
111 remote-tracking branch from an earlier fetch was still there, would
112 error out, primarily because the command was not told that it is
113 allowed to lose any information on our side. "git fetch --prune"
114 now can be used to remove 'frotz/nitfol' to make room to fetch and
115 store 'frotz' remote-tracking branch.
117 * "diff.orderfile=<file>" configuration variable can be used to
118 pretend as if the "-O<file>" option were given from the command
119 line of "git diff", etc.
121 * The negative pathspec syntax allows "git log -- . ':!dir'" to tell
122 us "I am interested in everything but 'dir' directory".
124 * "git difftool" shows how many different paths there are in total,
125 and how many of them have been shown so far, to indicate progress.
127 * "git push origin master" used to push our 'master' branch to update
128 the 'master' branch at the 'origin' repository. This has been
129 enhanced to use the same ref mapping "git push origin" would use to
130 determine what ref at the 'origin' to be updated with our 'master'.
131 For example, with this configuration
134 push = refs/heads/*:refs/review/*
136 that would cause "git push origin" to push out our local branches
137 to corresponding refs under refs/review/ hierarchy at 'origin',
138 "git push origin master" would update 'refs/review/master' over
139 there. Alternatively, if push.default is set to 'upstream' and our
140 'master' is set to integrate with 'topic' from the 'origin' branch,
141 running "git push origin" while on our 'master' would update their
142 'topic' branch, and running "git push origin master" while on any
143 of our branches does the same.
145 * "gitweb" learned to treat ref hierarchies other than refs/heads as
146 if they are additional branch namespaces (e.g. refs/changes/ in
149 * "git for-each-ref --format=..." learned a few formatting directives;
150 e.g. "%(color:red)%(HEAD)%(color:reset) %(refname:short) %(subject)".
152 * The command string given to "git submodule foreach" is passed
153 directly to the shell, without being eval'ed. This is a backward
154 incompatible change that may break existing users.
156 * "git log" and friends learned the "--exclude=<glob>" option, to
157 allow people to say "list history of all branches except those that
158 match this pattern" with "git log --exclude='*/*' --branches".
160 * "git rev-parse --parseopt" learned a new "--stuck-long" option to
161 help scripts parse options with an optional parameter.
163 * The "--tags" option to "git fetch" no longer tells the command to
164 fetch _only_ the tags. It instead fetches tags _in addition to_
165 what are fetched by the same command line without the option.
168 Performance, Internal Implementation, etc.
170 * When parsing a 40-hex string into the object name, the string is
171 checked to see if it can be interpreted as a ref so that a warning
172 can be given for ambiguity. The code kicked in even when the
173 core.warnambiguousrefs is set to false to squelch this warning, in
174 which case the cycles spent to look at the ref namespace were an
175 expensive no-op, as the result was discarded without being used.
177 * The naming convention of the packfiles has been updated; it used to
178 be based on the enumeration of names of the objects that are
179 contained in the pack, but now it also depends on how the packed
180 result is represented---packing the same set of objects using
181 different settings (or delta order) would produce a pack with
184 * "git diff --no-index" mode used to unnecessarily attempt to read
185 the index when there is one.
187 * The deprecated parse-options macro OPT_BOOLEAN has been removed;
188 use OPT_BOOL or OPT_COUNTUP in new code.
190 * A few duplicate implementations of prefix/suffix string comparison
191 functions have been unified to starts_with() and ends_with().
193 * The new PERLLIB_EXTRA makefile variable can be used to specify
194 additional directories Perl modules (e.g. the ones necessary to run
195 git-svn) are installed on the platform when building.
197 * "git merge-base" learned the "--fork-point" mode, that implements
198 the same logic used in "git pull --rebase" to find a suitable fork
199 point out of the reflog entries for the remote-tracking branch the
200 work has been based on. "git rebase" has the same logic that can be
201 triggered with the "--fork-point" option.
203 * A third-party "receive-pack" (the responder to "git push") can
204 advertise the "no-thin" capability to tell "git push" not to use
205 the thin-pack optimization. Our receive-pack has always been
206 capable of accepting and fattening a thin-pack, and will continue
207 not to ask "git push" to use a non-thin pack.
210 Also contains various documentation updates and code clean-ups.
216 Unless otherwise noted, all the fixes since v1.8.5 in the maintenance
217 track are contained in this release (see the maintenance releases' notes
220 * The pathspec matching code, while comparing two trees (e.g. "git
221 diff A B -- path1 path2") was too agrresive and failed to match
222 some paths when multiple pathspecs were involved.
223 (merge e4ddb05 as/tree-walk-fix-aggressive-short-cut later to maint).
225 * "git repack --max-pack-size=8g" stopped being parsed correctly when
226 the command was reimplemented in C.
227 (merge b861e23 sb/repack-in-c later to maint).
229 * An earlier update in v1.8.4.x to "git rev-list --objects" with
230 negative ref had performance regression.
231 (merge 200abe7 jk/mark-edges-uninteresting later to maint).
233 * A recent update to "git send-email" broke platforms where
234 /etc/ssl/certs/ directory exists, but it cannot used as SSL_ca_path
235 (e.g. Fedora rawhide).
236 (merge 01645b7 rk/send-email-ssl-cert later to maint).
238 * A handful of bugs around interpreting $branch@{upstream} notation
239 and its lookalike, when $branch part has interesting characters,
240 e.g. "@", and ":", have been fixed.
241 (merge 9892d5d jk/interpret-branch-name-fix later to maint).
243 * "git clone" would fail to clone from a repository that has a ref
244 directly under "refs/", e.g. "refs/stash", because different
245 validation paths do different things on such a refname. Loosen the
246 client side's validation to allow such a ref.
247 (merge 4c22408 jk/allow-fetch-onelevel-refname later to maint).
249 * "git log --left-right A...B" lost the "leftness" of commits
250 reachable from A when A is a tag as a side effect of a recent
251 bugfix. This is a regression in 1.8.4.x series.
252 (merge a743528 jc/revision-range-unpeel later to maint).
254 * documentations to "git pull" hinted there is an "-m" option because
255 it incorrectly shared the documentation with "git merge".
256 (merge 08f19cf jc/maint-pull-docfix later to maint).
258 * "git diff A B submod" and "git diff A B submod/" ought to have done
259 the same for a submodule "submod", but didn't.
261 * "git clone $origin foo\bar\baz" on Windows failed to create the
262 leading directories (i.e. a moral-equivalent of "mkdir -p").
264 * "submodule.*.update=checkout", when propagated from .gitmodules to
265 .git/config, turned into a "submodule.*.update=none", which did not
267 (merge efa8fd7 fp/submodule-checkout-mode later to maint).
269 * The implementation of 'git stash $cmd "stash@{...}"' did not quote
270 the stash argument properly and left it split at IFS whitespace.
271 (merge 2a07e43 ow/stash-with-ifs later to maint).
273 * The "--[no-]informative-errors" options to "git daemon" were parsed
274 a bit too loosely, allowing any other string after these option
276 (merge 82246b7 nd/daemon-informative-errors-typofix later to maint).
278 * There is no reason to have a hardcoded upper limit of the number of
279 parents for an octopus merge, created via the graft mechanism, but
281 (merge e228c17 js/lift-parent-count-limit later to maint).
283 * The basic test used to leave unnecessary trash directories in the
285 (merge 738a8be jk/test-framework-updates later to maint).
287 * "git merge-base --octopus" used to leave cleaning up suboptimal
288 result to the caller, but now it does the clean-up itself.
289 (merge 8f29299 bm/merge-base-octopus-dedup later to maint).
291 * A "gc" process running as a different user should be able to stop a
292 new "gc" process from starting, but it didn't.
293 (merge ed7eda8 km/gc-eperm later to maint).
295 * An earlier "clean-up" introduced an unnecessary memory leak.
296 (merge e1c1a32 jk/credential-plug-leak later to maint).
298 * "git add -A" (no other arguments) in a totally empty working tree
299 used to emit an error.
300 (merge 64ed07c nd/add-empty-fix later to maint).
302 * "git log --decorate" did not handle a tag pointed by another tag
304 (merge 5e1361c bc/log-decoration later to maint).
306 * When we figure out how many file descriptors to allocate for
307 keeping packfiles open, a system with non-working getrlimit() could
308 cause us to die(), but because we make this call only to get a
309 rough estimate of how many is available and we do not even attempt
310 to use up all file descriptors available ourselves, it is nicer to
311 fall back to a reasonable low value rather than dying.
312 (merge 491a8de jh/rlimit-nofile-fallback later to maint).
314 * read_sha1_file(), that is the workhorse to read the contents given
315 an object name, honoured object replacements, but there was no
316 corresponding mechanism to sha1_object_info() that was used to
317 obtain the metainfo (e.g. type & size) about the object. This led
318 callers to weird inconsistencies.
319 (merge 663a856 cc/replace-object-info later to maint).
321 * "git cat-file --batch=", an admittedly useless command, did not
323 (merge 6554dfa jk/cat-file-regression-fix later to maint).
325 * "git rev-parse <revs> -- <paths>" did not implement the usual
326 disambiguation rules the commands in the "git log" family used in
328 (merge 62f162f jk/rev-parse-double-dashes later to maint).
330 * "git mv A B/", when B does not exist as a directory, should error
332 (merge c57f628 mm/mv-file-to-no-such-dir-with-slash later to maint).
334 * A workaround to an old bug in glibc prior to glibc 2.17 has been
335 retired; this would remove a side effect of the workaround that
336 corrupts system error messages in non-C locales.
338 * SSL-related options were not passed correctly to underlying socket
339 layer in "git send-email".
340 (merge 5508f3e tr/send-email-ssl later to maint).
342 * "git commit -v" appends the patch to the log message before
343 editing, and then removes the patch when the editor returned
344 control. However, the patch was not stripped correctly when the
345 first modified path was a submodule.
346 (merge 1a72cfd jl/commit-v-strip-marker later to maint).
348 * "git fetch --depth=0" was a no-op, and was silently ignored.
349 Diagnose it as an error.
350 (merge 5594bca nd/transport-positive-depth-only later to maint).
352 * Remote repository URL expressed in scp-style host:path notation are
353 parsed more carefully (e.g. "foo/bar:baz" is local, "[::1]:/~user" asks
354 to connect to user's home directory on host at address ::1.
355 (merge a2036d7 tb/clone-ssh-with-colon-for-port later to maint).
357 * "git diff -- ':(icase)makefile'" was unnecessarily rejected at the
359 (merge 887c6c1 nd/magic-pathspec later to maint).
361 * "git cat-file --batch-check=ok" did not check the existence of
363 (merge 4ef8d1d sb/sha1-loose-object-info-check-existence later to maint).
365 * "git am --abort" sometimes complained about not being able to write
366 a tree with an 0{40} object in it.
367 (merge 77b43ca jk/two-way-merge-corner-case-fix later to maint).
369 * Two processes creating loose objects at the same time could have
370 failed unnecessarily when the name of their new objects started
371 with the same byte value, due to a race condition.
372 (merge b2476a6 jh/loose-object-dirs-creation-race later to maint).
projects / git / blob