1Git v1.8.4 Release Notes 2======================== 3 4Updates since v1.8.3 5-------------------- 6 7Foreign interfaces, subsystems and ports. 8 9 * Git-gui has been updated to its 0.18.0 version. 10 11 * MediaWiki remote helper (in contrib/) has been updated to use the 12 credential helper interface from Git.pm. 13 14 * Update build for Cygwin 1.[57]. Torsten Bögershausen reports that 15 this is fine with Cygwin 1.7 ($gmane/225824) so let's try moving it 16 ahead. 17 18 * The credential helper to talk to keychain on OS X (in contrib/) has 19 been updated to kick in not just when talking http/https but also 20 imap(s) and smtp. 21 22 * Remote transport helper has been updated to report errors and 23 maintain ref hierarchy used to keep track of its own state better. 24 25 * With "export" remote-helper protocol, (1) a push that tries to 26 update a remote ref whose name is different from the pushing side 27 does not work yet, and (2) the helper may not know how to do 28 --dry-run; these problematic cases are disabled for now. 29 30 * git-remote-hg/bzr (in contrib/) updates. 31 32 * git-remote-mw (in contrib/) hints users to check the certificate, 33 when https:// connection failed. 34 35 36UI, Workflows & Features 37 38 * Many tutorials teach users to set "color.ui" to "auto" as the first 39 thing after you set "user.name/email" to introduce yourselves to 40 Git. Now the variable defaults to "auto". 41 42 * "git status" learned status.branch and status.short configuration 43 variables to use --branch and --short options by default (override 44 with --no-branch and --no-short options from the command line). 45 46 * "git cmd <name>", when <name> happens to be a 40-hex string, 47 directly uses the 40-hex string as an object name, even if a ref 48 "refs/<some hierarchy>/<name>" exists. This disambiguation order 49 is unlikely to change, but we should warn about the ambiguity just 50 like we warn when more than one refs/ hierachies share the same 51 name. 52 53 * "git rebase" learned "--[no-]autostash" option to save local 54 changes instead of refusing to run (to which people's normal 55 response was to stash them and re-run). 56 57 * Instead of typing four capital letters "HEAD", you can say "@" now, 58 e.g. "git log @". 59 60 * "check-ignore" (new feature since 1.8.2) has been updated to work 61 more like "check-attr" over bidi-pipes. 62 63 * "git describe" learned "--first-parent" option to limit its closest 64 tagged commit search to the first-parent chain. 65 66 * "git merge foo" that might have meant "git merge origin/foo" is 67 diagnosed with a more informative error message. 68 69 * "git log -L<line>,<range>:<filename>" has been added. This may 70 still have leaks and rough edges, though. 71 72 * We used the approxidate() parser for "--expire=<timestamp>" options 73 of various commands, but it is better to treat --expire=all and 74 --expire=now a bit more specially than using the current timestamp. 75 "git gc" and "git reflog" have been updated with a new parsing 76 function for expiry dates. 77 78 * Updates to completion (both bash and zsh) helpers. 79 80 * The behaviour of the "--chain-reply-to" option of "git send-email" 81 have changed at 1.7.0, and we added a warning/advice message to 82 help users adjust to the new behaviour back then, but we kept it 83 around for too long. The message has finally been removed. 84 85 * "git fetch origin master" unlike "git fetch origin" or "git fetch" 86 did not update "refs/remotes/origin/master"; this was an early 87 design decision to keep the update of remote tracking branches 88 predictable, but in practice it turns out that people find it more 89 convenient to opportunistically update them whenever we have a 90 chance, and we have been updating them when we run "git push" which 91 already breaks the original "predictability" anyway. 92 93 * The configuration variable core.checkstat was advertised in the 94 documentation but the code expected core.statinfo instead. 95 For now, we accept both core.checkstat and core.statinfo, but the 96 latter will be removed in the longer term. 97 98 99Performance, Internal Implementation, etc. 100 101 * Uses of the platform fnmatch(3) function (many places in the code, 102 matching pathspec, .gitignore and .gitattributes to name a few) 103 have been replaced with wildmatch, allowing "foo/**/bar" that would 104 match foo/bar, foo/a/bar, foo/a/b/bar, etc. 105 106 * Memory ownership and lifetime rules for what for-each-ref feeds to 107 its callbacks have been clarified (in short, "you do not own it, so 108 make a copy if you want to keep it"). 109 110 * The revision traversal logic to improve culling of irrelevant 111 parents while traversing a mergy history has been updated. 112 113 * Some leaks in unpack-trees (used in merge, cherry-pick and other 114 codepaths) have been plugged. 115 116 * The codepath to read from marks files in fast-import/export did not 117 have to accept anything but 40-hex representation of the object 118 name. Further, fast-export did not need full in-core object 119 representation to have parsed wen reading from them. These 120 codepaths have been optimized by taking advantage of these access 121 patterns. 122 123 * Object lookup logic, when the object hashtable starts to become 124 crowded, has been optimized. 125 126 * When TEST_OUTPUT_DIRECTORY setting is used, it was handled somewhat 127 inconsistently between the test framework and t/Makefile, and logic 128 to summarize the results looked at a wrong place. 129 130 * "git clone" uses a lighter-weight implementation when making sure 131 that the history behind refs are complete. 132 133 * Many warnings from sparse source checker in compat/ area has been 134 squelched. 135 136 * The code to reading and updating packed-refs file has been updated, 137 correcting corner case bugs. 138 139 140Also contains various documentation updates and code clean-ups. 141 142 143Fixes since v1.8.3 144------------------ 145 146Unless otherwise noted, all the fixes since v1.8.3 in the maintenance 147track are contained in this release (see release notes to them for 148details). 149 150 * Logic used by git-send-email to suppress cc mishandled names like 151 "A U. Thor" <author@example.xz>, where the human readable part 152 needs to be quoted (the user input may not have the double quotes 153 around the name, and comparison was done between quoted and 154 unquoted strings). 155 (merge 1495266 mt/send-email-cc-match-fix later to maint). 156 157 * Call to discard_cache/discard_index (used when we use different 158 contents of the index in-core, in many operations like commit, 159 apply, and merge) used to leak memory that held the array of index 160 entries, which has been plugged. 161 (merge a0fc4db rs/discard-index-discard-array later to maint). 162 163 * "gitweb" forgot to clear a global variable $search_regexp upon each 164 request, mistakenly carrying over the previous search to a new one 165 when used as a persistent CGI. 166 (merge ca7a5dc cm/gitweb-project-list-persistent-cgi-fix later to maint). 167 168 * The wildmatch engine did not honor WM_CASEFOLD option correctly. 169 (merge b79c0c3 ar/wildmatch-foldcase later to maint). 170 171 * "git log -c --follow $path" segfaulted upon hitting the commit that 172 renamed the $path being followed. 173 (merge 46ec510 cb/log-follow-with-combined later to maint). 174 175 * When a reflog notation is used for implicit "current branch", we 176 did not say which branch and worse said "branch ''". 177 (merge 305ebea rr/die-on-missing-upstream later to maint). 178 179 * "difftool --dir-diff" did not copy back changes made by the 180 end-user in the diff tool backend to the working tree in some 181 cases. 182 (merge 32eaf1d ks/difftool-dir-diff-copy-fix later to maint). 183 184 * "git push $there HEAD:branch" did not resolve HEAD early enough, so 185 it was easy to flip it around while push is still going on and push 186 out a branch that the user did not originally intended when the 187 command was started. 188 (merge 0f075b2 rr/push-head later to maint). 189 190 * The bash prompt code (in contrib/) displayed the name of the branch 191 being rebased when "rebase -i/-m/-p" modes are in use, but not the 192 plain vanilla "rebase". 193 (merge 1306321 fc/show-branch-in-rebase-am later to maint). 194 195 * Handling of negative exclude pattern for directories "!dir" was 196 broken in the update to v1.8.3. 197 (merge c3c327d kb/status-ignored-optim-2 later to maint). 198 199 * zsh prompt script that borrowed from bash prompt script did not 200 work due to slight differences in array variable notation between 201 these two shells. 202 (merge d0583da tg/maint-zsh-svn-remote-prompt later to maint). 203 204 * An entry for "file://" scheme in the enumeration of URL types Git 205 can take in the HTML documentation was made into a clickable link 206 by mistake. 207 (merge 4c32e36 nd/urls-doc-no-file-hyperlink-fix later to maint). 208 209 * "git push --[no-]verify" was not documented. 210 (merge 90d32d1 tr/push-no-verify-doc later to maint). 211 212 * Stop installing the git-remote-testpy script that is only used for 213 testing. 214 (merge 416fda6 fc/makefile later to maint). 215 216 * "git commit --allow-empty-message -m ''" should not start an 217 editor. 218 (merge 2520677 rs/commit-m-no-edit later to maint). 219 220 * "git merge @{-1}~22" was rewritten to "git merge frotz@{1}~22" 221 incorrectly when your previous branch was "frotz" (it should be 222 rewritten to "git merge frotz~22" instead). 223 (merge 84cf246 jc/strbuf-branchname-fix later to maint). 224 225 * "git diff -c -p" was not showing a deleted line from a hunk when 226 another hunk immediately begins where the earlier one ends. 227 (merge aac3857 mk/combine-diff-context-horizon-fix later to maint). 228 229 * "git log --ancestry-path A...B" did not work as expected, as it did 230 not pay attention to the fact that the merge base between A and B 231 was the bottom of the range being specified. 232 (merge a765499 kb/ancestry-path-threedots later to maint). 233 234 * Mac OS X does not like to write(2) more than INT_MAX number of 235 bytes; work it around by chopping write(2) into smaller pieces. 236 (merge 6c642a8 fc/macos-x-clipped-write later to maint). 237 238 * Newer MacOS X encourages the programs to compile and link with 239 their CommonCrypto, not with OpenSSL. 240 (merge be4c828 da/darwin later to maint). 241 242 * "git clone foo/bar:baz" cannot be a request to clone from a remote 243 over git-over-ssh specified in the scp style. This case is now 244 detected and clones from a local repository at "foo/bar:baz". 245 (merge 6000334 nd/clone-local-with-colon later to maint). 246 247 * When $HOME is misconfigured to point at an unreadable directory, we 248 used to complain and die. Loosen the check. 249 (merge 4698c8f jn/config-ignore-inaccessible later to maint). 250 251 * "git subtree" (in contrib/) had one codepath with loose error 252 checks to lose data at the remote side. 253 (merge 3212d56 jk/subtree-do-not-push-if-split-fails later to maint). 254 255 * "git fetch" into a shallow repository from a repository that does 256 not know about the shallow boundary commits (e.g. a different fork 257 from the repository the current shallow repository was cloned from) 258 did not work correctly. 259 (merge 71d5f93 mh/fetch-into-shallow later to maint). 260 261 * "git checkout foo" DWIMs the intended "upstream" and turns it into 262 "git checkout -t -b foo remotes/origin/foo". This codepath has been 263 updated to correctly take existing remote definitions into account. 264 (merge 229177a jh/checkout-auto-tracking later to maint).