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