1Git v1.8.3 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 the current branch to the branch with the same 12name, only when the current branch is set to integrate with that 13remote branch. There is a user preference configuration variable 14"push.default" to change this. If you are an old-timer who is used 15to the "matching" semantics, you can set it to "matching" to keep the 16traditional behaviour. If you want to live in the future early, 17you can set it to "simple" today without waiting for Git 2.0. 18 19When "git add -u" and "git add -A", that does not specify what paths 20to add on the command line is run from inside a subdirectory, these 21commands will operate on the entire tree in Git 2.0 for consistency 22with "git commit -a" and other commands. Because there will be no 23mechanism to make "git add -u" behave as if "git add -u .", it is 24important for those who are used to "git add -u" (without pathspec) 25updating the index only for paths in the current subdirectory to start 26training their fingers to explicitly say "git add -u ." when they mean 27it before Git 2.0 comes. 28 29 30Updates since v1.8.2 31-------------------- 32 33UI, Workflows & Features 34 35 * "git help" learned "-g" option to show the list of guides just like 36 list of commands are given with "-a". 37 38 * A triangular "pull from one place, push to another place" workflow 39 is supported better by new remote.pushdefault (overrides the 40 "origin" thing) and branch.*.pushremote (overrides the 41 branch.*.remote) configuration variables. 42 43 * "git status" learned to report that you are in the middle of a 44 revert session, just like it does for a cherry-pick and a bisect 45 session. 46 47 * The handling by "git branch --set-upstream-to" against various forms 48 of erroneous inputs was suboptimal and has been improved. 49 50 * When the interactive access to git-shell is not enabled, it issues 51 a message meant to help the system administrator to enable it. 52 An explicit way to help the end users who connect to the service by 53 issuing custom messages to refuse such an access has been added. 54 55 * In addition to the case where the user edits the log message with 56 the "e)dit" option of "am -i", replace the "Applying: this patch" 57 message with the final log message contents after applymsg hook 58 munges it. 59 60 * "git status" suggests users to look into using --untracked=no option 61 when it takes too long. 62 63 * "git status" shows a bit more information to "git status" during a 64 rebase/bisect session. 65 66 * "git fetch" learned to fetch a commit at the tip of an unadvertised 67 ref by specifying a raw object name from the command line when the 68 server side supports this feature. 69 70 * Output from "git log --graph" works better with submodule log 71 output now. 72 73 * "git count-objects -v" learned to report leftover temporary 74 packfiles and other garbage in the object store. 75 76 * A new read-only credential helper (in contrib/) to interact with 77 the .netrc/.authinfo files has been added. 78 79 * "git send-email" can be used with the credential helper system. 80 81 * There was no Porcelain way to say "I no longer am interested in 82 this submodule", once you express your interest in a submodule with 83 "submodule init". "submodule deinit" is the way to do so. 84 85 * "git pull --rebase" learned to pass "-v/-q" options to underlying 86 "git rebase". 87 88 * The new "--follow-tags" option tells "git push" to push relevant 89 annotated tags when pushing branches out. 90 91 * "git merge" and "git pull" can optionally be told to inspect and 92 reject when merging a commit that does not carry a trusted GPG 93 signature. 94 95 * "git mergetool" now feeds files to the "p4merge" backend in the 96 order that matches the p4 convention, where "theirs" is usually 97 shown on the left side, which is the opposite from other backend 98 expects. 99 100 * "show/log" now honors gpg.program configuration just like other 101 parts of the code that use GnuPG. 102 103 * "git log" that shows the difference between the parent and the 104 child has been optimized somewhat. 105 106 * "git difftool" allows the user to write into the temporary files 107 being shown; if the user makes changes to the working tree at the 108 same time, one of the changes has to be lost in such a case, but it 109 tells the user what happened and refrains from overwriting the copy 110 in the working tree. 111 112 * There was no good way to ask "I have a random string that came from 113 outside world. I want to turn it into a 40-hex object name while 114 making sure such an object exists". A new peeling suffix ^{object} 115 can be used for that purpose, together with "rev-parse --verify". 116 117 118Performance, Internal Implementation, etc. 119 120 * Updates for building under msvc. 121 122 * The logic to coalesce the same lines removed from the parents in 123 the output from "diff -c/--cc" has been updated, but with an O(n^2) 124 complexity, so this might turn out to be undesirable. 125 126 * The code to enforce permission bits on files in $GIT_DIR/ for 127 shared repositories have been simplified. 128 129 * A few codepaths knew how much data they need to put in the 130 hashtables they use upfront, but still started from a small table 131 repeatedly growing and rehashing. 132 133 * The API to walk reflog entries from the latest to older, which was 134 necessary for operations such as "git checkout -", was cumbersome 135 to use correctly and also inefficient. 136 137 * Codepaths that inspect log-message-to-be and decide when to add a 138 new Signed-off-by line in various commands have been consolidated. 139 140 * The pkt-line API, implementation and its callers have been cleaned 141 up to make them more robust. 142 143 * Cygwin port has a faster-but-lying lstat(2) emulation whose 144 incorrectness does not matter in practice except for a few 145 codepaths, and setting permission bits to directories is a codepath 146 that needs to use a more correct one. 147 148 * "git checkout" had repeated pathspec matches on the same paths, 149 which have been consolidated. Also a bug in "git checkout dir/" 150 that is started from an unmerged index has been fixed. 151 152 * A few bugfixes to "git rerere" working on corner case merge 153 conflicts have been applied. 154 155 156Also contains minor documentation updates and code clean-ups. 157 158 159Fixes since v1.8.2 160------------------ 161 162Unless otherwise noted, all the fixes since v1.8.2 in the maintenance 163track are contained in this release (see release notes to them for 164details). 165 166 * Perl scripts like "git-svn" closed (not redirecting to /dev/null) 167 the standard error stream, which is not a very smart thing to do. 168 Later open may return file descriptor #2 for unrelated purpose, and 169 error reporting code may write into them. 170 (merge a749c0b tr/perl-keep-stderr-open later to maint). 171 172 * "git show-branch" was not prepared to show a very long run of 173 ancestor operators e.g. foobar^2~2^2^2^2...^2~4 correctly. 174 (merge aaa07e3 jk/show-branch-strbuf later to maint). 175 176 * "git diff --diff-algorithm algo" is also understood as "git diff 177 --diff-algorithm=algo". 178 (merge 0895c6d jk/diff-algo-finishing-touches later to maint). 179 180 * The new core.commentchar configuration was not applied to a few 181 places. 182 (merge 89c3bbd rt/commentchar-fmt-merge-msg later to maint). 183 184 * "git bundle" did not like a bundle created using a commit without 185 any message as its one of the prerequistes. 186 (merge 5446e33 lf/bundle-with-tip-wo-message later to maint). 187 188 * "git log -S/-G" started paying attention to textconv filter, but 189 there was no way to disable this. Make it honor --no-textconv 190 option. 191 (merge 61690bf sr/log-SG-no-textconv later to maint). 192 193 * When used with "-d temporary-directory" option, "git filter-branch" 194 failed to come back to the original working tree to perform the 195 final clean-up procedure. 196 (merge 9727601 jk/filter-branch-come-back-to-original later to maint). 197 198 * "git merge $(git rev-parse v1.8.2)" behaved quite differently from 199 "git merge v1.8.2", as if v1.8.2 were written as v1.8.2^0 and did 200 not pay much attention to the annotated tag payload. Make the code 201 notice the type of the tag object, in addition to the dwim_ref() 202 based classification the current code uses (i.e. the name appears 203 in refs/tags/) to decide when to special case merging of tags. 204 (merge a38d3d7 jc/merge-tag-object later to maint). 205 206 * Fix 1.8.1.x regression that stopped matching "dir" (without 207 trailing slash) to a directory "dir". 208 (merge efa5f82 jc/directory-attrs-regression-fix later to maint-1.8.1). 209 210 * "git apply --whitespace=fix" was not prepared to see a line getting 211 longer after fixing whitespaces (e.g. tab-in-indent aka Python). 212 (merge 329b26e jc/apply-ws-fix-tab-in-indent later to maint-1.8.1). 213 214 * The prompt string generator (in contrib/completion/) did not notice 215 when we are in a middle of a "git revert" session. 216 (merge 3ee4452 rr/prompt-revert-head later to maint). 217 218 * "submodule summary --summary-limit" option did not support 219 "--option=value" form. 220 (merge 862ae6c rs/submodule-summary-limit later to maint). 221 222 * "index-pack --fix-thin" used an uninitialized value to compute 223 delta depths of objects it appends to the resulting pack. 224 (merge 57165db jk/index-pack-correct-depth-fix later to maint). 225 226 * "index-pack --verify-stat" used a few counters outside protection 227 of mutex, possibly showing incorrect numbers. 228 (merge 8f82aad nd/index-pack-threaded-fixes later to maint). 229 230 * The code to keep track of what directory names are known to Git on 231 platforms with case insensitive filesystems can get confused upon a 232 hash collision between these pathnames and looped forever. 233 234 * Annotated tags outside refs/tags/ hierarchy were not advertised 235 correctly to the ls-remote and fetch with recent version of Git. 236 237 * Recent optimization broke shallow clones. 238 (merge f59de5d jk/peel-ref later to maint). 239 240 * "git cmd -- ':(top'" was not diagnosed as an invalid syntax, and 241 instead the parser kept reading beyond the end of the string. 242 243 * "git tag -f <tag>" always said "Updated tag '<tag>'" even when 244 creating a new tag (i.e. not overwriting nor updating). 245 246 * "git p4" did not behave well when the path to the root of the P4 247 client was not its real path. 248 (merge bbd8486 pw/p4-symlinked-root later to maint). 249 250 * "git archive" reports a failure when asked to create an archive out 251 of an empty tree. It would be more intuitive to give an empty 252 archive back in such a case. 253 254 * When "format-patch" quoted a non-ascii strings on the header files, 255 it incorrectly applied rfc2047 and chopped a single character in 256 the middle of it. 257 258 * An aliased command spawned from a bare repository that does not say 259 it is bare with "core.bare = yes" is treated as non-bare by mistake. 260 261 * In "git reflog expire", REACHABLE bit was not cleared from the 262 correct objects. 263 264 * The logic used by "git diff -M --stat" to shorten the names of 265 files before and after a rename did not work correctly when the 266 common prefix and suffix between the two filenames overlapped. 267 268 * The "--match=<pattern>" option of "git describe", when used with 269 "--all" to allow refs that are not annotated tags to be used as a 270 base of description, did not restrict the output from the command 271 to those that match the given pattern. 272 273 * Clarify in the documentation "what" gets pushed to "where" when the 274 command line to "git push" does not say these explicitly. 275 276 * The "--color=<when>" argument to the commands in the diff family 277 was described poorly. 278 279 * The arguments given to pre-rebase hook were not documented. 280 281 * The v4 index format was not documented. 282 283 * The "--match=<pattern>" argument "git describe" takes uses glob 284 pattern but it wasn't obvious from the documentation. 285 286 * Some sources failed to compile on systems that lack NI_MAXHOST in 287 their system header (e.g. z/OS). 288 289 * Add an example use of "--env-filter" in "filter-branch" 290 documentation. 291 292 * "git bundle verify" did not say "records a complete history" for a 293 bundle that does not have any prerequisites. 294 295 * In the v1.8.0 era, we changed symbols that do not have to be global 296 to file scope static, but a few functions in graph.c were used by 297 CGit from sideways bypassing the entry points of the API the 298 in-tree users use. 299 300 * "git update-index -h" did not do the usual "-h(elp)" thing. 301 302 * "git index-pack" had a buffer-overflow while preparing an 303 informational message when the translated version of it was too 304 long. 305 306 * 'git commit -m "$msg"' used to add an extra newline even when 307 $msg already ended with one. 308 309 * The SSL peer verification done by "git imap-send" did not ask for 310 Server Name Indication (RFC 4366), failing to connect SSL/TLS 311 sites that serve multiple hostnames on a single IP. 312 313 * perl/Git.pm::cat_blob slurped everything in core only to write it 314 out to a file descriptor, which was not a very smart thing to do. 315 316 * "git branch" did not bother to check nonsense command line 317 parameters and issue errors in many cases. 318 319 * Verification of signed tags were not done correctly when not in C 320 or en/US locale. 321 322 * Some platforms and users spell UTF-8 differently; retry with the 323 most official "UTF-8" when the system does not understand the 324 user-supplied encoding name that are the common alternative 325 spellings of UTF-8. 326 327 * When export-subst is used, "zip" output recorded incorrect 328 size of the file. 329 330 * "git am $maildir/" applied messages in an unexpected order; sort 331 filenames read from the maildir/ in a way that is more likely to 332 sort messages in the order the writing MUA meant to, by sorting 333 numeric segment in numeric order and non-numeric segment in 334 alphabetical order. 335 336 * "git submodule update", when recursed into sub-submodules, did not 337 accumulate the prefix paths.