1Git v1.8.4 Release Notes 2======================== 3 4Updates since v1.8.3 5-------------------- 6 7Foreign interface 8 9 * Remote transport helper has been updated to report errors and 10 maintain ref hierarchy used to keep track of its own state better. 11 12 13UI, Workflows & Features 14 15 * "check-ignore" (new feature since 1.8.2) has been updated to work 16 more like "check-attr" over bidi-pipes. 17 18 * "git describe" learned "--first-parent" option to limit its closest 19 tagged commit search to the first-parent chain. 20 21 * "git merge foo" that might have meant "git merge origin/foo" is 22 diagnosed with a more informative error message. 23 24 * "git log -L<line>,<range>:<filename>" has been added. This may 25 still have leaks and rough edges, though. 26 27 * We used the approxidate() parser for "--expire=<timestamp>" options 28 of various commands, but it is better to treat --expire=all and 29 --expire=now a bit more specially than using the current timestamp. 30 "git gc" and "git reflog" have been updated with a new parsing 31 function for expiry dates. 32 33 * Updates to completion (both bash and zsh) helpers. 34 35 * The behaviour of the "--chain-reply-to" option of "git send-email" 36 have changed at 1.7.0, and we added a warning/advice message to 37 help users adjust to the new behaviour back then, but we kept it 38 around for too long. The message has finally been removed. 39 40 * "git fetch origin master" unlike "git fetch origin" or "git fetch" 41 did not update "refs/remotes/origin/master"; this was an early 42 design decision to keep the update of remote tracking branches 43 predictable, but in practice it turns out that people find it more 44 convenient to opportunistically update them whenever we have a 45 chance, and we have been updating them when we run "git push" which 46 already breaks the original "predictability" anyway. 47 48 * The configuration variable core.checkstat was advertised in the 49 documentation but the code expected core.statinfo instead. 50 For now, we accept both core.checkstat and core.statinfo, but the 51 latter will be removed in the longer term. 52 53 54Performance, Internal Implementation, etc. 55 56 * The codepath to read from marks files in fast-import/export did not 57 have to accept anything but 40-hex representation of the object 58 name. Further, fast-export did not need full in-core object 59 representation to have parsed wen reading from them. These 60 codepaths have been optimized by taking advantage of these access 61 patterns. 62 63 * Object lookup logic, when the object hashtable starts to become 64 crowded, has been optimized. 65 66 * When TEST_OUTPUT_DIRECTORY setting is used, it was handled somewhat 67 inconsistently between the test framework and t/Makefile, and logic 68 to summarize the results looked at a wrong place. 69 70 * Many warnings from sparse source checker in compat/ area has been 71 squelched. 72 73 * The code to reading and updating packed-refs file has been updated, 74 correcting corner case bugs. 75 76 77Also contains various documentation updates and code clean-ups. 78 79 80Fixes since v1.8.3 81------------------ 82 83Unless otherwise noted, all the fixes since v1.8.3 in the maintenance 84track are contained in this release (see release notes to them for 85details). 86 87 * Handling of negative exclude pattern for directories "!dir" was 88 broken in the update to v1.8.3. 89 (merge c3c327d kb/status-ignored-optim-2 later to maint). 90 91 * zsh prompt script that borrowed from bash prompt script did not 92 work due to slight differences in array variable notation between 93 these two shells. 94 (merge d0583da tg/maint-zsh-svn-remote-prompt later to maint). 95 96 * An entry for "file://" scheme in the enumeration of URL types Git 97 can take in the HTML documentation was made into a clickable link 98 by mistake. 99 (merge 4c32e36 nd/urls-doc-no-file-hyperlink-fix later to maint). 100 101 * "git push --[no-]verify" was not documented. 102 (merge 90d32d1 tr/push-no-verify-doc later to maint). 103 104 * Stop installing the git-remote-testpy script that is only used for 105 testing. 106 (merge 416fda6 fc/makefile later to maint). 107 108 * "git commit --allow-empty-message -m ''" should not start an 109 editor. 110 (merge 2520677 rs/commit-m-no-edit later to maint). 111 112 * "git merge @{-1}~22" was rewritten to "git merge frotz@{1}~22" 113 incorrectly when your previous branch was "frotz" (it should be 114 rewritten to "git merge frotz~22" instead). 115 (merge 84cf246 jc/strbuf-branchname-fix later to maint). 116 117 * "git diff -c -p" was not showing a deleted line from a hunk when 118 another hunk immediately begins where the earlier one ends. 119 (merge aac3857 mk/combine-diff-context-horizon-fix later to maint). 120 121 * "git log --ancestry-path A...B" did not work as expected, as it did 122 not pay attention to the fact that the merge base between A and B 123 was the bottom of the range being specified. 124 (merge a765499 kb/ancestry-path-threedots later to maint). 125 126 * Mac OS X does not like to write(2) more than INT_MAX number of 127 bytes; work it around by chopping write(2) into smaller pieces. 128 (merge 6c642a8 fc/macos-x-clipped-write later to maint). 129 130 * Newer MacOS X encourages the programs to compile and link with 131 their CommonCrypto, not with OpenSSL. 132 (merge be4c828 da/darwin later to maint). 133 134 * "git clone foo/bar:baz" cannot be a request to clone from a remote 135 over git-over-ssh specified in the scp style. This case is now 136 detected and clones from a local repository at "foo/bar:baz". 137 (merge 6000334 nd/clone-local-with-colon later to maint). 138 139 * When $HOME is misconfigured to point at an unreadable directory, we 140 used to complain and die. Loosen the check. 141 (merge 4698c8f jn/config-ignore-inaccessible later to maint). 142 143 * "git subtree" (in contrib/) had one codepath with loose error 144 checks to lose data at the remote side. 145 (merge 3212d56 jk/subtree-do-not-push-if-split-fails later to maint). 146 147 * "git fetch" into a shallow repository from a repository that does 148 not know about the shallow boundary commits (e.g. a different fork 149 from the repository the current shallow repository was cloned from) 150 did not work correctly. 151 (merge 71d5f93 mh/fetch-into-shallow later to maint). 152 153 * "git checkout foo" DWIMs the intended "upstream" and turns it into 154 "git checkout -t -b foo remotes/origin/foo". This codepath has been 155 updated to correctly take existing remote definitions into account. 156 (merge 229177a jh/checkout-auto-tracking later to maint).