1Git 1.7.12.1 Release Notes 2========================== 3 4Fixes since v1.7.12 5------------------- 6 7 * "ciabot" script (in contrib/) has been updated with extensive 8 documentation. 9 10 * The "--rebase" option to "git pull" can be abbreviated to "-r", 11 but we didn't document it. 12 13 * It was generally understood that "--long-option"s to many of our 14 subcommands can be abbreviated to the unique prefix, but it was not 15 easy to find it described for new readers of the documentation set. 16 17 * The synopsis said "checkout [-B branch]" to make it clear the 18 branch name is a parameter to the option, but the heading for the 19 option description was "-B::", not "-B branch::", making the 20 documentation misleading. 21 22 * The "--topo-order", "--date-order" (and the lack of either means 23 the default order) options to "rev-list" and "log" family of 24 commands were poorly described in the documentation. 25 26 * Older parts of the documentation described as if having a regular 27 file in .git/refs/ hierarchy were the only way to have branches and 28 tags, which is not true for quite some time. 29 30 * A utility shell function test_seq has been added as a replacement 31 for the 'seq' utility found on some platforms. 32 33 * Compatibility wrapper to learn the maximum number of file 34 descriptors we can open around sysconf(_SC_OPEN_MAX) and 35 getrlimit(RLIMIT_NO_FILE) has been introduced for portability. 36 37 * We used curl_easy_strerror() without checking version of cURL, 38 breaking the build for versions before curl 7.12.0. 39 40 * Code to work around MacOS X UTF-8 gotcha has been cleaned up. 41 42 * Fallback 'getpass' implementation made unportable use of stdio API. 43 44 * "git apply -p0" did not parse pathnames on "diff --git" line 45 correctly. This caused patches that had pathnames in no other 46 places to be mistakenly rejected (most notably, binary patch that 47 does not rename nor change mode). Textual patches, renames or mode 48 changes have preimage and postimage pathnames in different places 49 in a form that can be parsed unambiguously and did not suffer from 50 this problem. 51 52 * "git commit --amend" let the user edit the log message and then 53 died when the human-readable committer name was given 54 insufficiently by getpwent(3). 55 56 * Some capabilities were asked by fetch-pack even when upload-pack 57 did not advertise that they are available. fetch-pack has been 58 fixed not to do so. 59 60 * "git for-each-ref" did not currectly support more than one --sort 61 option. 62 63 * "git log .." errored out saying it is both rev range and a path 64 when there is no disambiguating "--" is on the command line. 65 Update the command line parser to interpret ".." as a path in such 66 a case. 67 68 * "git prune" without "-v" used to warn about leftover temporary 69 files (which is an indication of an earlier aborted operation). 70 71 * Pushing to smart HTTP server with recent Git fails without having 72 the username in the URL to force authentication, if the server is 73 configured to allow GET anonymously, while requiring authentication 74 for POST. 75 76 * The reflog entries left by "git rebase" and "git rebase -i" were 77 inconsistent (the interactive one gave an abbreviated object name). 78 79 * When the user exports a non-default IFS without HT, scripts that 80 rely on being able to parse "ls-files -s | while read a b c..." 81 started to fail. Protect them from such a misconfiguration. 82 83 * When "git push" triggered the automatic gc on the receiving end, a 84 message from "git prune" that said it was removing cruft leaked to 85 the standard output, breaking the communication protocol. 86 87 * "git diff" had a confusion between taking data from a path in the 88 working tree and taking data from an object that happens to have 89 name 0{40} recorded in a tree. 90 91 * "git send-email" did not unquote encoded words that appear on the 92 header correctly, and lost "_" from strings. 93 94 * When the user gives an argument that can be taken as both a 95 revision name and a pathname without disambiguating with "--", we 96 used to give a help message "Use '--' to separate". The message 97 has been clarified to show where that '--' goes on the command 98 line. 99 100 * "gitweb" when used with PATH_INFO failed to notice directories with 101 SP (and other characters that need URL-style quoting) in them.