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