1Git v1.8.1 Release Notes 2======================== 3 4Backward compatibility notes 5---------------------------- 6 7In the next major release (not *this* one), we will change the 8behavior of the "git push" command. 9 10When "git push [$there]" does not say what to push, we have used the 11traditional "matching" semantics so far (all your branches were sent 12to the remote as long as there already are branches of the same name 13over there). We will use the "simple" semantics that pushes the 14current branch to the branch with the same name, only when the current 15branch is set to integrate with that remote branch. There is a user 16preference configuration variable "push.default" to change this, and 17"git push" will warn about the upcoming change until you set this 18variable in this release. 19 20"git branch --set-upstream" is deprecated and may be removed in a 21relatively distant future. "git branch [-u|--set-upstream-to]" has 22been introduced with a saner order of arguments. 23 24 25Updates since v1.8.0 26-------------------- 27 28UI, Workflows & Features 29 30 * Command-line completion scripts for tcsh and zsh have been added. 31 32 * A new remote-helper interface for Mercurial has been added to 33 contrib/remote-helpers. 34 35 * We used to have a workaround for a bug in ancient "less" that 36 causes it to exit without any output when the terminal is resized. 37 The bug has been fixed in "less" version 406 (June 2007), and the 38 workaround has been removed in this release. 39 40 * Some documentation pages that used to ship only in the plain text 41 format are now formatted in HTML as well. 42 43 * "git-prompt" scriptlet (in contrib/completion) can be told to paint 44 pieces of the hints in the prompt string in colors. 45 46 * A new configuration variable "diff.context" can be used to 47 give the default number of context lines in the patch output, to 48 override the hardcoded default of 3 lines. 49 50 * When "git checkout" checks out a branch, it tells the user how far 51 behind (or ahead) the new branch is relative to the remote tracking 52 branch it builds upon. The message now also advises how to sync 53 them up by pushing or pulling. 54 55 * "git config --get" used to diagnose presence of multiple 56 definitions of the same variable in the same configuration file as 57 an error, but it now applies the "last one wins" rule used by the 58 internal configuration logic. Strictly speaking, this may be an 59 API regression but it is expected that nobody will notice it in 60 practice. 61 62 * "git log -p -S<string>" now looks for the <string> after applying 63 the textconv filter (if defined); earlier it inspected the contents 64 of the blobs without filtering. 65 66 * "git format-patch" learned the "--notes=<ref>" option to give 67 notes for the commit after the three-dash lines in its output. 68 69 * "git log --grep=<pcre>" learned to honor the "grep.patterntype" 70 configuration set to "perl". 71 72 * "git replace -d <object>" now interprets <object>, instead of only 73 accepting full hex object name. 74 75 * "git rm $submodule" used to punt on removing a submodule working 76 tree to avoid losing the repository embedded in it. Because 77 recent git uses a mechanism to separate the submodule repository 78 from the submodule working tree, "git rm" learned to detect this 79 case and removes the submodule working tree when it is safe. 80 81 * "git send-email" used to prompt for the sender address, even when 82 the committer identify is well specified (e.g. via user.name and 83 user.email configuration variables). The command no longer gives 84 this prompt when not necessary. 85 86 * "git send-email" did not allow non-address garbage strings to 87 appear after addresses on Cc: lines in the patch files (and when 88 told to pick them up to find more recipients), e.g. 89 90 Cc: Stable Kernel <stable@k.org> # for v3.2 and up 91 92 The command now strips " # for v3.2 and up" part before adding the 93 remainder of this line to the list of recipients. 94 95 * "git submodule add" learned to add a new submodule at the same 96 path as the path where an unrelated submodule was bound to in an 97 existing revision via the "--name" option. 98 99 * "git submodule sync" learned the "--recursive" option. 100 101 * "diff.submodule" configuration variable can be used to give custom 102 default value to the "git diff --submodule" option. 103 104 * "git symbolic-ref" learned the "-d $symref" option to delete the 105 named symbolic ref, which is more intuitive way to spell it than 106 "update-ref -d --no-deref". 107 108 109Foreign Interface 110 111 * "git cvsimport" can be told to record timezones (other than GMT) 112 per-author via its author info file. 113 114 * The remote helper interface to interact with subversion 115 repositories (one of the GSoC 2012 projects) has been merged. 116 117 118Performance, Internal Implementation, etc. 119 120 * Compilation on Cygwin with newer header files are supported now. 121 122 * The logic to generate the initial advertisement from 123 "upload-pack" (what is invoked by "git fetch" on the other side 124 of the connection) to list what refs are available in the 125 repository has been optimized. 126 127 * The logic to find set of attributes that match a given path has 128 been optimized. 129 130 * Use preloadindex in "git diff-index" and "git update-index", which 131 has a nice speedup on systems with slow stat calls (and even on 132 Linux). 133 134 135Also contains minor documentation updates and code clean-ups. 136 137 138Fixes since v1.8.0 139------------------ 140 141Unless otherwise noted, all the fixes since v1.8.0 in the maintenance 142track are contained in this release (see release notes to them for 143details). 144 145 * The configuration parser had an unnecessary hardcoded limit on 146 variable names that was not checked consistently. 147 (merge 0971e99 bw/config-lift-variable-name-length-limit later to maint). 148 149 * The "say" function in the test scaffolding incorrectly allowed 150 "echo" to interpret "\a" as if it were a C-string asking for a 151 BEL output. 152 (merge 7bc0911 jc/test-say-color-avoid-echo-escape later to maint). 153 154 * "git mergetool" feeds /dev/null as a common ancestor when dealing 155 with an add/add conflict, but p4merge backend cannot handle 156 it. Work it around by passing a temporary empty file. 157 (merge 3facc60 da/mergetools-p4 later to maint). 158 159 * "git log -F -E --grep='<ere>'" failed to use the given <ere> 160 pattern as extended regular expression, and instead looked for the 161 string literally. 162 (merge 727b6fc jc/grep-pcre-loose-ends~1 later to maint). 163 164 * "git grep -e pattern <tree>" asked the attribute system to read 165 "<tree>:.gitattributes" file in the working tree, which was 166 nonsense. 167 (merge 55c6168 nd/grep-true-path later to maint). 168 169 * A symbolic ref refs/heads/SYM was not correctly removed with "git 170 branch -d SYM"; the command removed the ref pointed by SYM 171 instead. 172 (merge 13baa9f rs/branch-del-symref later to maint). 173 174 * Update "remote tracking branch" in the documentation to 175 "remote-tracking branch". 176 (merge a6d3bde mm/maint-doc-remote-tracking later to maint). 177 178 * "git pull --rebase" run while the HEAD is detached tried to find 179 the upstream branch of the detached HEAD (which by definition 180 does not exist) and emitted unnecessary error messages. 181 (merge e980765 ph/pull-rebase-detached later to maint). 182 183 * The refs/replace hierarchy was not mentioned in the 184 repository-layout docs. 185 (merge 11fbe18 po/maint-refs-replace-docs later to maint). 186 187 * Various rfc2047 quoting issues around a non-ASCII name on the 188 From: line in the output from format-patch have been corrected. 189 (merge 25dc8da js/format-2047 later to maint). 190 191 * Sometimes curl_multi_timeout() function suggested a wrong timeout 192 value when there is no file descriptor to wait on and the http 193 transport ended up sleeping for minutes in select(2) system call. 194 A workaround has been added for this. 195 (merge 7202b81 sz/maint-curl-multi-timeout later to maint). 196 197 * For a fetch refspec (or the result of applying wildcard on one), 198 we always want the RHS to map to something inside "refs/" 199 hierarchy, but the logic to check it was not exactly right. 200 (merge 5c08c1f jc/maint-fetch-tighten-refname-check later to maint). 201 202 * "git diff -G<pattern>" did not honor textconv filter when looking 203 for changes. 204 (merge b1c2f57 jk/maint-diff-grep-textconv later to maint). 205 206 * Some HTTP servers ask for auth only during the actual packing phase 207 (not in ls-remote phase); this is not really a recommended 208 configuration, but the clients used to fail to authenticate with 209 such servers. 210 (merge 2e736fd jk/maint-http-half-auth-fetch later to maint). 211 212 * "git p4" used to try expanding malformed "$keyword$" that spans 213 across multiple lines. 214 (merge 6b2bf41 pw/maint-p4-rcs-expansion-newline later to maint). 215 216 * Syntax highlighting in "gitweb" was not quite working. 217 (merge 048b399 rh/maint-gitweb-highlight-ext later to maint). 218 219 * RSS feed from "gitweb" had a xss hole in its title output. 220 (merge 0f0ecf6 jk/maint-gitweb-xss later to maint). 221 222 * "git config --path $key" segfaulted on "[section] key" (a boolean 223 "true" spelled without "=", not "[section] key = true"). 224 (merge 962c38e cn/config-missing-path later to maint). 225 226 * "git checkout -b foo" while on an unborn branch did not say 227 "Switched to a new branch 'foo'" like other cases. 228 (merge afa8c07 jk/checkout-out-of-unborn later to maint). 229 230 * We failed to mention a file without any content change but whose 231 permission bit was modified, or (worse yet) a new file without any 232 content in the "git diff --stat" output. 233 (merge de9095955 lt/diff-stat-show-0-lines later to maint). 234 235 * When "--stat-count" hides a diffstat for binary contents, the total 236 number of added and removed lines at the bottom was computed 237 incorrectly. 238 (merge de9095955 lt/diff-stat-show-0-lines later to maint). 239 240 * When "--stat-count" hides a diffstat for unmerged paths, the total 241 number of affected files at the bottom of the "diff --stat" output 242 was computed incorrectly. 243 (merge de9095955 lt/diff-stat-show-0-lines later to maint). 244 245 * "diff --shortstat" miscounted the total number of affected files 246 when there were unmerged paths. 247 (merge de9095955 lt/diff-stat-show-0-lines later to maint). 248 249 * "update-ref -d --deref SYM" to delete a ref through a symbolic ref 250 that points to it did not remove it correctly. 251 (merge b274a71 jh/update-ref-d-through-symref later to maint).