1Git v1.8.3.3 Release Notes 2========================== 3 4Fixes since v1.8.3.2 5-------------------- 6 7 * "git apply" parsed patches that add new files, generated by programs 8 other than Git, incorrectly. This is an old breakage in v1.7.11. 9 10 * Older cURL wanted piece of memory we call it with to be stable, but 11 we updated the auth material after handing it to a call. 12 13 * "git pull" into nothing trashed "local changes" that were in the 14 index. 15 16 * Many "git submodule" operations did not work on a submodule at a 17 path whose name is not in ASCII. 18 19 * "cherry-pick" had a small leak in its error codepath. 20 21 * Logic used by git-send-email to suppress cc mishandled names like 22 "A U. Thor" <author@example.xz>, where the human readable part 23 needs to be quoted (the user input may not have the double quotes 24 around the name, and comparison was done between quoted and 25 unquoted strings). It also mishandled names that need RFC2047 26 quoting. 27 28 * "gitweb" forgot to clear a global variable $search_regexp upon each 29 request, mistakenly carrying over the previous search to a new one 30 when used as a persistent CGI. 31 32 * The wildmatch engine did not honor WM_CASEFOLD option correctly. 33 34 * "git log -c --follow $path" segfaulted upon hitting the commit that 35 renamed the $path being followed. 36 37 * When a reflog notation is used for implicit "current branch", 38 e.g. "git log @{u}", we did not say which branch and worse said 39 "branch ''" in the error messages. 40 41 * Mac OS X does not like to write(2) more than INT_MAX number of 42 bytes; work it around by chopping write(2) into smaller pieces. 43 44 * Newer MacOS X encourages the programs to compile and link with 45 their CommonCrypto, not with OpenSSL. 46 47Also contains various minor documentation updates.