1Git v1.7.11.6 Release Notes 2=========================== 3 4Fixes since v1.7.11.5 5--------------------- 6 7 * "ciabot" script (in contrib/) has been updated with extensive 8 documentation. 9 10 * "git foo" errored out with "Not a directory" when the user had a 11 non-directory on $PATH, and worse yet it masked an alias "foo" from 12 running. 13 14 * When the user exports a non-default IFS without HT, scripts that 15 rely on being able to parse "ls-files -s | while read a b c..." 16 started to fail. Protect them from such a misconfiguration. 17 18 * When the user gives an argument that can be taken as both a 19 revision name and a pathname without disambiguating with "--", we 20 used to give a help message "Use '--' to separate". The message 21 has been clarified to show where that '--' goes on the command 22 line. 23 24 * Documentation for the configuration file format had a confusing 25 example. 26 27 * Older parts of the documentation described as if having a regular 28 file in .git/refs/ hierarchy were the only way to have branches and 29 tags, which is not true for quite some time. 30 31 * It was generally understood that "--long-option"s to many of our 32 subcommands can be abbreviated to the unique prefix, but it was not 33 easy to find it described for new readers of the documentation set. 34 35 * The "--topo-order", "--date-order" (and the lack of either means 36 the default order) options to "rev-list" and "log" family of 37 commands were poorly described in the documentation. 38 39 * "git commit --amend" let the user edit the log message and then 40 died when the human-readable committer name was given 41 insufficiently by getpwent(3). 42 43 * The exit status code from "git config" was way overspecified while 44 being incorrect. The implementation has been updated to give the 45 documented status for a case that was documented, and introduce a 46 new code for "all other errors". 47 48 * The output from "git diff -B" for a file that ends with an 49 incomplete line did not put "\ No newline..." on a line of its own. 50 51 * "git diff" had a confusion between taking data from a path in the 52 working tree and taking data from an object that happens to have 53 name 0{40} recorded in a tree. 54 55 * The "--rebase" option to "git pull" can be abbreviated to "-r", 56 but we didn't document it. 57 58 * When "git push" triggered the automatic gc on the receiving end, a 59 message from "git prune" that said it was removing cruft leaked to 60 the standard output, breaking the communication protocol. 61 62 * The reflog entries left by "git rebase" and "git rebase -i" were 63 inconsistent (the interactive one gave an abbreviated object name). 64 65 * "git send-email" did not unquote encoded words that appear on the 66 header correctly, and lost "_" from strings. 67 68 * "git stash apply/pop" did not trigger "rerere" upon conflicts 69 unlike other mergy operations. 70 71 * "git submodule <cmd> path" did not error out when the path to the 72 submodule was misspelt. 73 74 * "git submodule update -f" did not update paths in the working tree 75 that has local changes. 76 (merge 01d4721 sz/submodule-force-update later to maint). 77 78 * "gitweb" when used with PATH_INFO failed to notice directories with 79 SP (and other characters that need URL-style quoting) in them. 80 81 * Fallback 'getpass' implementation made unportable use of stdio API. 82 83 * A utility shell function test_seq has been added as a replacement 84 for the 'seq' utility found on some platforms.