1 Git v1.8.4 Release Notes
2 ========================
7 Foreign interfaces and ports.
9 * Update build for Cygwin 1.[57]. Torsten Bögershausen reports that
10 this is fine with Cygwin 1.7 ($gmane/225824) so let's try moving it
13 * The credential helper to talk to keychain on OS X (in contrib/) has
14 been updated to kick in not just when talking http/https but also
17 * Remote transport helper has been updated to report errors and
18 maintain ref hierarchy used to keep track of its own state better.
20 * With "export" remote-helper protocol, (1) a push that tries to
21 update a remote ref whose name is different from the pushing side
22 does not work yet, and (2) the helper may not know how to do
23 --dry-run; these problematic cases are disabled for now.
25 * git-remote-hg/bzr (in contrib/) updates.
27 * git-remote-mw (in contrib/) hints users to check the certificate,
28 when https:// connection failed.
31 UI, Workflows & Features
33 * "git cmd <name>", when <name> happens to be a 40-hex string,
34 directly uses the 40-hex string as an object name, even if a ref
35 "refs/<some hierarchy>/<name>" exists. This disambiguation order
36 is unlikely to change, but we should warn about the ambiguity just
37 like we warn when more than one refs/ hierachies share the same
40 * "git rebase" learned "--[no-]autostash" option to save local
41 changes instead of refusing to run (to which people's normal
42 response was to stash them and re-run).
44 * Instead of typing four capital letters "HEAD", you can say "@" now,
47 * "check-ignore" (new feature since 1.8.2) has been updated to work
48 more like "check-attr" over bidi-pipes.
50 * "git describe" learned "--first-parent" option to limit its closest
51 tagged commit search to the first-parent chain.
53 * "git merge foo" that might have meant "git merge origin/foo" is
54 diagnosed with a more informative error message.
56 * "git log -L<line>,<range>:<filename>" has been added. This may
57 still have leaks and rough edges, though.
59 * We used the approxidate() parser for "--expire=<timestamp>" options
60 of various commands, but it is better to treat --expire=all and
61 --expire=now a bit more specially than using the current timestamp.
62 "git gc" and "git reflog" have been updated with a new parsing
63 function for expiry dates.
65 * Updates to completion (both bash and zsh) helpers.
67 * The behaviour of the "--chain-reply-to" option of "git send-email"
68 have changed at 1.7.0, and we added a warning/advice message to
69 help users adjust to the new behaviour back then, but we kept it
70 around for too long. The message has finally been removed.
72 * "git fetch origin master" unlike "git fetch origin" or "git fetch"
73 did not update "refs/remotes/origin/master"; this was an early
74 design decision to keep the update of remote tracking branches
75 predictable, but in practice it turns out that people find it more
76 convenient to opportunistically update them whenever we have a
77 chance, and we have been updating them when we run "git push" which
78 already breaks the original "predictability" anyway.
80 * The configuration variable core.checkstat was advertised in the
81 documentation but the code expected core.statinfo instead.
82 For now, we accept both core.checkstat and core.statinfo, but the
83 latter will be removed in the longer term.
86 Performance, Internal Implementation, etc.
88 * Some leaks in unpack-trees (used in merge, cherry-pick and other
89 codepaths) have been plugged.
91 * The codepath to read from marks files in fast-import/export did not
92 have to accept anything but 40-hex representation of the object
93 name. Further, fast-export did not need full in-core object
94 representation to have parsed wen reading from them. These
95 codepaths have been optimized by taking advantage of these access
98 * Object lookup logic, when the object hashtable starts to become
99 crowded, has been optimized.
101 * When TEST_OUTPUT_DIRECTORY setting is used, it was handled somewhat
102 inconsistently between the test framework and t/Makefile, and logic
103 to summarize the results looked at a wrong place.
105 * "git clone" uses a lighter-weight implementation when making sure
106 that the history behind refs are complete.
108 * Many warnings from sparse source checker in compat/ area has been
111 * The code to reading and updating packed-refs file has been updated,
112 correcting corner case bugs.
115 Also contains various documentation updates and code clean-ups.
121 Unless otherwise noted, all the fixes since v1.8.3 in the maintenance
122 track are contained in this release (see release notes to them for
125 * "gitweb" forgot to clear a global variable $search_regexp upon each
126 request, mistakenly carrying over the previous search to a new one
127 when used as a persistent CGI.
128 (merge ca7a5dc cm/gitweb-project-list-persistent-cgi-fix later to maint).
130 * The wildmatch engine did not honor WM_CASEFOLD option correctly.
131 (merge b79c0c3 ar/wildmatch-foldcase later to maint).
133 * "git log -c --follow $path" segfaulted upon hitting the commit that
134 renamed the $path being followed.
135 (merge 46ec510 cb/log-follow-with-combined later to maint).
137 * When a reflog notation is used for implicit "current branch", we
138 did not say which branch and worse said "branch ''".
139 (merge 305ebea rr/die-on-missing-upstream later to maint).
141 * "difftool --dir-diff" did not copy back changes made by the
142 end-user in the diff tool backend to the working tree in some
144 (merge 32eaf1d ks/difftool-dir-diff-copy-fix later to maint).
146 * "git push $there HEAD:branch" did not resolve HEAD early enough, so
147 it was easy to flip it around while push is still going on and push
148 out a branch that the user did not originally intended when the
150 (merge 0f075b2 rr/push-head later to maint).
152 * The bash prompt code (in contrib/) displayed the name of the branch
153 being rebased when "rebase -i/-m/-p" modes are in use, but not the
154 plain vanilla "rebase".
155 (merge 1306321 fc/show-branch-in-rebase-am later to maint).
157 * Handling of negative exclude pattern for directories "!dir" was
158 broken in the update to v1.8.3.
159 (merge c3c327d kb/status-ignored-optim-2 later to maint).
161 * zsh prompt script that borrowed from bash prompt script did not
162 work due to slight differences in array variable notation between
164 (merge d0583da tg/maint-zsh-svn-remote-prompt later to maint).
166 * An entry for "file://" scheme in the enumeration of URL types Git
167 can take in the HTML documentation was made into a clickable link
169 (merge 4c32e36 nd/urls-doc-no-file-hyperlink-fix later to maint).
171 * "git push --[no-]verify" was not documented.
172 (merge 90d32d1 tr/push-no-verify-doc later to maint).
174 * Stop installing the git-remote-testpy script that is only used for
176 (merge 416fda6 fc/makefile later to maint).
178 * "git commit --allow-empty-message -m ''" should not start an
180 (merge 2520677 rs/commit-m-no-edit later to maint).
182 * "git merge @{-1}~22" was rewritten to "git merge frotz@{1}~22"
183 incorrectly when your previous branch was "frotz" (it should be
184 rewritten to "git merge frotz~22" instead).
185 (merge 84cf246 jc/strbuf-branchname-fix later to maint).
187 * "git diff -c -p" was not showing a deleted line from a hunk when
188 another hunk immediately begins where the earlier one ends.
189 (merge aac3857 mk/combine-diff-context-horizon-fix later to maint).
191 * "git log --ancestry-path A...B" did not work as expected, as it did
192 not pay attention to the fact that the merge base between A and B
193 was the bottom of the range being specified.
194 (merge a765499 kb/ancestry-path-threedots later to maint).
196 * Mac OS X does not like to write(2) more than INT_MAX number of
197 bytes; work it around by chopping write(2) into smaller pieces.
198 (merge 6c642a8 fc/macos-x-clipped-write later to maint).
200 * Newer MacOS X encourages the programs to compile and link with
201 their CommonCrypto, not with OpenSSL.
202 (merge be4c828 da/darwin later to maint).
204 * "git clone foo/bar:baz" cannot be a request to clone from a remote
205 over git-over-ssh specified in the scp style. This case is now
206 detected and clones from a local repository at "foo/bar:baz".
207 (merge 6000334 nd/clone-local-with-colon later to maint).
209 * When $HOME is misconfigured to point at an unreadable directory, we
210 used to complain and die. Loosen the check.
211 (merge 4698c8f jn/config-ignore-inaccessible later to maint).
213 * "git subtree" (in contrib/) had one codepath with loose error
214 checks to lose data at the remote side.
215 (merge 3212d56 jk/subtree-do-not-push-if-split-fails later to maint).
217 * "git fetch" into a shallow repository from a repository that does
218 not know about the shallow boundary commits (e.g. a different fork
219 from the repository the current shallow repository was cloned from)
220 did not work correctly.
221 (merge 71d5f93 mh/fetch-into-shallow later to maint).
223 * "git checkout foo" DWIMs the intended "upstream" and turns it into
224 "git checkout -t -b foo remotes/origin/foo". This codepath has been
225 updated to correctly take existing remote definitions into account.
226 (merge 229177a jh/checkout-auto-tracking later to maint).