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