1Git v1.8.5 Release Notes 2======================== 3 4Backward compatibility notes (for Git 2.0) 5------------------------------------------ 6 7When "git push [$there]" does not say what to push, we have used the 8traditional "matching" semantics so far (all your branches were sent 9to the remote as long as there already are branches of the same name 10over there). In Git 2.0, the default will change to the "simple" 11semantics that pushes: 12 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 16 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. 19 20Use the user preference configuration variable "push.default" to 21change this. If you are an old-timer who is used to the "matching" 22semantics, you can set the variable to "matching" to keep the 23traditional behaviour. If you want to live in the future early, you 24can set it to "simple" today without waiting for Git 2.0. 25 26When "git add -u" (and "git add -A") is run inside a subdirectory and 27does not specify which paths to add on the command line, it 28will operate on the entire tree in Git 2.0 for consistency 29with "git commit -a" and other commands. There will be no 30mechanism to make plain "git add -u" behave like "git add -u .". 31Current users of "git add -u" (without a pathspec) should start 32training their fingers to explicitly say "git add -u ." 33before Git 2.0 comes. A warning is issued when these commands are 34run without a pathspec and when you have local changes outside the 35current directory, because the behaviour in Git 2.0 will be different 36from today's version in such a situation. 37 38In Git 2.0, "git add <path>" will behave as "git add -A <path>", so 39that "git add dir/" will notice paths you removed from the directory 40and record the removal. Versions before Git 2.0, including this 41release, will keep ignoring removals, but the users who rely on this 42behaviour are encouraged to start using "git add --ignore-removal <path>" 43now before 2.0 is released. 44 45 46Updates since v1.8.4 47-------------------- 48 49Foreign interfaces, subsystems and ports. 50 51 * remote-hg remote helper misbehaved when interacting with a local Hg 52 repository relative to the home directory, e.g. "clone hg::~/there". 53 54 * imap-send ported to OS X uses Apple's security framework instead of 55 OpenSSL one. 56 57 * Subversion 1.8.0 that was recently released breaks older subversion 58 clients coming over http/https in various ways. 59 60 * "git fast-import" treats an empty path given to "ls" as the root of 61 the tree. 62 63 64UI, Workflows & Features 65 66 * Magic pathspecs like ":(icase)makefile" that matches both 67 Makefile and makefile can be used in more places. 68 69 * The "http.*" variables can now be specified per URL that the 70 configuration applies. For example, 71 72 [http] 73 sslVerify = true 74 [http "https://weak.example.com/"] 75 sslVerify = false 76 77 would flip http.sslVerify off only when talking to that specified 78 site. 79 80 * "git mv A B" when moving a submodule A has been taught to 81 relocate its working tree and to adjust the paths in the 82 .gitmodules file. 83 84 * "git blame" can now take more than one -L option to discover the 85 origin of multiple blocks of the lines. 86 87 * The http transport clients can optionally ask to save cookies 88 with http.savecookies configuration variable. 89 90 * "git push" learned a more fine grained control over a blunt 91 "--force" when requesting a non-fast-forward update with the 92 "--force-with-lease=<refname>:<expected object name>" option. 93 94 * "git diff --diff-filter=<classes of changes>" can now take 95 lowercase letters (e.g. "--diff-filter=d") to mean "show 96 everything but these classes". "git diff-files -q" is now a 97 deprecated synonym for "git diff-files --diff-filter=d". 98 99 * "git fetch" (hence "git pull" as well) learned to check 100 "fetch.prune" and "remote.*.prune" configuration variables and 101 to behave as if the "--prune" command line option was given. 102 103 * "git check-ignore -z" applied the NUL termination to both its input 104 (with --stdin) and its output, but "git check-attr -z" ignored the 105 option on the output side. Make both honor -z on the input and 106 output side the same way. 107 108 * "git whatchanged" may still be used by old timers, but mention of 109 it in documents meant for new users will only waste readers' time 110 wonderig what the difference is between it and "git log". Make it 111 less prominent in the general part of the documentation and explain 112 that it is merely a "git log" with different default behaviour in 113 its own document. 114 115 116Performance, Internal Implementation, etc. 117 118 * Many commands use --dashed-option as a operation mode selector 119 (e.g. "git tag --delete") that the user can use at most one 120 (e.g. "git tag --delete --verify" is a nonsense) and you cannot 121 negate (e.g. "git tag --no-delete" is a nonsense). parse-options 122 API learned a new OPT_CMDMODE macro to make it easier to implement 123 such a set of options. 124 125 * OPT_BOOLEAN() in parse-options API was misdesigned to be "counting 126 up" but many subcommands expect it to behave as "on/off". Update 127 them to use OPT_BOOL() which is a proper boolean. 128 129 * "git gc" exits early without doing a double-work when it detects 130 that another instance of itself is already running. 131 132 * Under memory pressure and/or file descriptor pressure, we used to 133 close pack windows that are not used and also closed filehandle to 134 an open but unused packfiles. These are now controlled separately 135 to better cope with the load. 136 137Also contains various documentation updates and code clean-ups. 138 139 140Fixes since v1.8.4 141------------------ 142 143Unless otherwise noted, all the fixes since v1.8.4 in the maintenance 144track are contained in this release (see release notes to them for 145details). 146 147 * The mailmap support code read past the allocated buffer when the 148 mailmap file ended with an incomplete line. 149 (merge f972a16 jk/mailmap-incomplete-line later to maint). 150 151 * We used to send a large request to read(2)/write(2) as a single 152 system call, which was bad from the latency point of view when 153 the operation needs to be killed, and also triggered an error on 154 broken 64-bit systems that refuse to take more than 2GB read or 155 write in one go. 156 (merge a487916 sp/clip-read-write-to-8mb later to maint). 157 158 * "git fetch" that auto-followed tags incorrectly reused the 159 connection with Git-aware transport helper (like the sample "ext::" 160 helper shipped with Git). 161 (merge 0f73f8b jc/transport-do-not-use-connect-twice-in-fetch later to maint). 162 163 * "git log --full-diff -- <pathspec>" showed a huge diff for paths 164 outside the given <pathspec> for each commit, instead of showing 165 the change relative to the parent of the commit. "git reflog -p" 166 had a similar problem. 167 (merge 838f9a1 tr/log-full-diff-keep-true-parents later to maint). 168 169 * Setting submodule.*.path configuration variable to true (without 170 giving "= value") caused Git to segfault. 171 (merge 4b05440 jl/some-submodule-config-are-not-boolean later to maint). 172 173 * "git rebase -i" (there could be others, as the root cause is pretty 174 generic) fed a random, data dependeant string to 'echo' and 175 expects it to come out literally, corrupting its error message. 176 (merge 89b0230 mm/no-shell-escape-in-die-message later to maint). 177 178 * Some people still use rather old versions of bash, which cannot 179 grok some constructs like 'printf -v varname' the prompt and 180 completion code started to use recently. 181 (merge a44aa69 bc/completion-for-bash-3.0 later to maint). 182 183 * Code to read configuration from a blob object did not compile on 184 platforms with fgetc() etc. implemented as macros. 185 (merge 49d6cfa hv/config-from-blob later to maint-1.8.3). 186 187 * The recent "short-cut clone connectivity check" topic broke a 188 shallow repository when a fetch operation tries to auto-follow tags. 189 (merge 6da8bdc nd/fetch-pack-shallow-fix later to maint-1.8.3).