| blob | 3b43a61d85ab6afed943b2160eb5b3669698d047 |
1 Git v1.8.5 Release Notes
2 ========================
4 Backward compatibility notes (for Git 2.0)
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 will change to the "simple"
11 semantics that 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 Use the user preference configuration variable "push.default" to
21 change this. If you are an old-timer who is used to the "matching"
22 semantics, you can set the variable to "matching" to keep the
23 traditional behaviour. If you want to live in the future early, you
24 can set it to "simple" today without waiting for Git 2.0.
26 When "git add -u" (and "git add -A") is run inside a subdirectory and
27 does not specify which paths to add on the command line, it
28 will operate on the entire tree in Git 2.0 for consistency
29 with "git commit -a" and other commands. There will be no
30 mechanism to make plain "git add -u" behave like "git add -u .".
31 Current users of "git add -u" (without a pathspec) should start
32 training their fingers to explicitly say "git add -u ."
33 before Git 2.0 comes. A warning is issued when these commands are
34 run without a pathspec and when you have local changes outside the
35 current directory, because the behaviour in Git 2.0 will be different
36 from today's version in such a situation.
38 In Git 2.0, "git add <path>" will behave as "git add -A <path>", so
39 that "git add dir/" will notice paths you removed from the directory
40 and record the removal. Versions before Git 2.0, including this
41 release, will keep ignoring removals, but the users who rely on this
42 behaviour are encouraged to start using "git add --ignore-removal <path>"
43 now before 2.0 is released.
46 Updates since v1.8.4
47 --------------------
49 Foreign interfaces, subsystems and ports.
51 * remote-hg remote helper misbehaved when interacting with a local Hg
52 repository relative to the home directory, e.g. "clone hg::~/there".
54 * imap-send ported to OS X uses Apple's security framework instead of
55 OpenSSL one.
57 * Subversion 1.8.0 that was recently released breaks older subversion
58 clients coming over http/https in various ways.
60 * "git fast-import" treats an empty path given to "ls" as the root of
61 the tree.
64 UI, Workflows & Features
66 * "git check-ignore -z" applied the NUL termination to both its input
67 (with --stdin) and its output, but "git check-attr -z" ignored the
68 option on the output side. Make both honor -z on the input and
69 output side the same way.
71 * "git whatchanged" may still be used by old timers, but mention of
72 it in documents meant for new users will only waste readers' time
73 wonderig what the difference is between it and "git log". Make it
74 less prominent in the general part of the documentation and explain
75 that it is merely a "git log" with different default behaviour in
76 its own document.
79 Performance, Internal Implementation, etc.
81 * Many commands use --dashed-option as a operation mode selector
82 (e.g. "git tag --delete") that the user can use at most one
83 (e.g. "git tag --delete --verify" is a nonsense) and you cannot
84 negate (e.g. "git tag --no-delete" is a nonsense). parse-options
85 API learned a new OPT_CMDMODE macro to make it easier to implement
86 such a set of options.
88 * OPT_BOOLEAN() in parse-options API was misdesigned to be "counting
89 up" but many subcommands expect it to behave as "on/off". Update
90 them to use OPT_BOOL() which is a proper boolean.
92 * "git gc" exits early without doing a double-work when it detects
93 that another instance of itself is already running.
95 * Under memory pressure and/or file descriptor pressure, we used to
96 close pack windows that are not used and also closed filehandle to
97 an open but unused packfiles. These are now controlled separately
98 to better cope with the load.
100 Also contains various documentation updates and code clean-ups.
103 Fixes since v1.8.4
104 ------------------
106 Unless otherwise noted, all the fixes since v1.8.4 in the maintenance
107 track are contained in this release (see release notes to them for
108 details).
110 * Setting submodule.*.path configuration variable to true (without
111 giving "= value") caused Git to segfault.
112 (merge 4b05440 jl/some-submodule-config-are-not-boolean later to maint).
114 * "git rebase -i" (there could be others, as the root cause is pretty
115 generic) fed a random, data dependeant string to 'echo' and
116 expects it to come out literally, corrupting its error message.
117 (merge 89b0230 mm/no-shell-escape-in-die-message later to maint).
119 * Some people still use rather old versions of bash, which cannot
120 grok some constructs like 'printf -v varname' the prompt and
121 completion code started to use recently.
122 (merge a44aa69 bc/completion-for-bash-3.0 later to maint).
124 * Code to read configuration from a blob object did not compile on
125 platforms with fgetc() etc. implemented as macros.
126 (merge 49d6cfa hv/config-from-blob later to maint-1.8.3).
128 * The recent "short-cut clone connectivity check" topic broke a
129 shallow repository when a fetch operation tries to auto-follow tags.
130 (merge 6da8bdc nd/fetch-pack-shallow-fix later to maint-1.8.3).