1Git v1.7.11.6 Release Notes 2=========================== 3 4Fixes since v1.7.11.5 5--------------------- 6 7This consists primarily of documentation updates and low-impact code 8clarification and bugfixes. 9 10 - "ciabot" script (in contrib/) has been updated with extensive 11 documentation. 12 13 - The "--rebase" option to "git pull" can be abbreviated to "-r", 14 but we didn't document it. 15 16 - It was generally understood that "--long-option"s to many of our 17 subcommands can be abbreviated to the unique prefix, but it was not 18 easy to find it described for new readers of the documentation set. 19 20 - The "--topo-order", "--date-order" (and the lack of either means 21 the default order) options to "rev-list" and "log" family of 22 commands were poorly described in the documentation. 23 24 - Older parts of the documentation described as if having a regular 25 file in .git/refs/ hierarchy were the only way to have branches and 26 tags, which is not true for quite some time. 27 28 - A utility shell function test_seq has been added as a replacement 29 for the 'seq' utility found on some platforms. 30 31 - Fallback 'getpass' implementation made unportable use of stdio API. 32 33 - "git commit --amend" let the user edit the log message and then 34 died when the human-readable committer name was given 35 insufficiently by getpwent(3). 36 37 - The reflog entries left by "git rebase" and "git rebase -i" were 38 inconsistent (the interactive one gave an abbreviated object name). 39 40 - When the user exports a non-default IFS without HT, scripts that 41 rely on being able to parse "ls-files -s | while read a b c..." 42 started to fail. Protect them from such a misconfiguration. 43 44 - When "git push" triggered the automatic gc on the receiving end, a 45 message from "git prune" that said it was removing cruft leaked to 46 the standard output, breaking the communication protocol. 47 48 - "git diff" had a confusion between taking data from a path in the 49 working tree and taking data from an object that happens to have 50 name 0{40} recorded in a tree. 51 52 - "git send-email" did not unquote encoded words that appear on the 53 header correctly, and lost "_" from strings. 54 55 - When the user gives an argument that can be taken as both a 56 revision name and a pathname without disambiguating with "--", we 57 used to give a help message "Use '--' to separate". The message 58 has been clarified to show where that '--' goes on the command 59 line. 60 61 - "gitweb" when used with PATH_INFO failed to notice directories with 62 SP (and other characters that need URL-style quoting) in them.