| blob | 7120c220e4758af837685707bdd7c52293b8f837 |
1 Git v1.9 Release Notes
2 ======================
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 A handful of ancient commands that have long been deprecated are
23 finally gone (repo-config, tar-tree, lost-found, and peek-remote).
26 Backward compatibility notes (for Git 2.0)
27 ------------------------------------------
29 When "git push [$there]" does not say what to push, we have used the
30 traditional "matching" semantics so far (all your branches were sent
31 to the remote as long as there already are branches of the same name
32 over there). In Git 2.0, the default will change to the "simple"
33 semantics, which pushes:
35 - only the current branch to the branch with the same name, and only
36 when the current branch is set to integrate with that remote
37 branch, if you are pushing to the same remote as you fetch from; or
39 - only the current branch to the branch with the same name, if you
40 are pushing to a remote that is not where you usually fetch from.
42 Use the user preference configuration variable "push.default" to
43 change this. If you are an old-timer who is used to the "matching"
44 semantics, you can set the variable to "matching" to keep the
45 traditional behaviour. If you want to live in the future early, you
46 can set it to "simple" today without waiting for Git 2.0.
48 When "git add -u" (and "git add -A") is run inside a subdirectory and
49 does not specify which paths to add on the command line, it
50 will operate on the entire tree in Git 2.0 for consistency
51 with "git commit -a" and other commands. There will be no
52 mechanism to make plain "git add -u" behave like "git add -u .".
53 Current users of "git add -u" (without a pathspec) should start
54 training their fingers to explicitly say "git add -u ."
55 before Git 2.0 comes. A warning is issued when these commands are
56 run without a pathspec and when you have local changes outside the
57 current directory, because the behaviour in Git 2.0 will be different
58 from today's version in such a situation.
60 In Git 2.0, "git add <path>" will behave as "git add -A <path>", so
61 that "git add dir/" will notice paths you removed from the directory
62 and record the removal. Versions before Git 2.0, including this
63 release, will keep ignoring removals, but the users who rely on this
64 behaviour are encouraged to start using "git add --ignore-removal <path>"
65 now before 2.0 is released.
67 The default prefix for "git svn" will change in Git 2.0. For a long
68 time, "git svn" created its remote-tracking branches directly under
69 refs/remotes, but it will place them under refs/remotes/origin/ unless
70 it is told otherwise with its --prefix option.
73 Updates since v1.8.5
74 --------------------
76 Foreign interfaces, subsystems and ports.
78 * The HTTP transport, when talking GSS-Negotiate, uses "100
79 Continue" response to avoid having to rewind and resend a large
80 payload, which may not be always doable.
82 * Various bugfixes to remote-bzr and remote-hg (in contrib/).
85 UI, Workflows & Features
87 * "git for-each-ref --format=..." learned a few formatting directives;
88 e.g. "%(color:red)%(HEAD)%(color:reset) %(refname:short) %(subject)".
90 * The command string given to "git submodule foreach" is passed
91 directly to the shell, without being eval'ed. This is a backward
92 incompatible change that may break existing users.
94 * "git log" and friends learned the "--exclude=<glob>" option, to
95 allow people to say "list history of all branches except those that
96 match this pattern" with "git log --exclude='*/*' --branches".
98 * "git rev-parse --parseopt" learned a new "--stuck-long" option to
99 help scripts parse options with an optional parameter.
101 * The "--tags" option to "git fetch" no longer tells the command to
102 fetch _only_ the tags. It instead fetches tags _in addition to_
103 what are fetched by the same command line without the option.
106 Performance, Internal Implementation, etc.
108 * The new PERLLIB_EXTRA makefile variable can be used to specify
109 additional directories Perl modules (e.g. the ones necessary to run
110 git-svn) are installed on the platform when building.
112 * "git merge-base" learned the "--fork-point" mode, that implements
113 the same logic used in "git pull --rebase" to find a suitable fork
114 point out of the reflog entries for the remote-tracking branch the
115 work has been based on.
117 * A third-party "receive-pack" (the responder to "git push") can
118 advertise the "no-thin" capability to tell "git push" not to use
119 the thin-pack optimization. Our receive-pack has always been
120 capable of accepting and fattening a thin-pack, and will continue
121 not to ask "git push" to use a non-thin pack.
124 Also contains various documentation updates and code clean-ups.
127 Fixes since v1.8.5
128 ------------------
130 Unless otherwise noted, all the fixes since v1.8.5 in the maintenance
131 track are contained in this release (see the maintenance releases' notes
132 for details).
134 * "git diff -- ':(icase)makefile'" was unnecessarily rejected at the
135 command line parser.
136 (merge 887c6c1 nd/magic-pathspec later to maint).
138 * "git cat-file --batch-check=ok" did not check the existence of
139 the named object.
140 (merge 4ef8d1d sb/sha1-loose-object-info-check-existence later to maint).
142 * "git am --abort" sometimes complained about not being able to write
143 a tree with an 0{40} object in it.
144 (merge 77b43ca jk/two-way-merge-corner-case-fix later to maint).
146 * Two processes creating loose objects at the same time could have
147 failed unnecessarily when the name of their new objects started
148 with the same byte value, due to a race condition.
149 (merge b2476a6 jh/loose-object-dirs-creation-race later to maint).