1Git v1.7.10.2 Release Notes 2=========================== 3 4Fixes since v1.7.10.1 5--------------------- 6 7 * The test scaffolding for git-daemon was flaky. 8 9 * The test scaffolding for fast-import was flaky. 10 11 * The filesystem boundary was not correctly reported when .git directory 12 discovery stopped at a mount point. 13 14 * HTTP transport that requires authentication did not work correctly when 15 multiple connections are used simultaneously. 16 17 * In the older days, the header "Conflicts:" in "cherry-pick" and "merge" 18 was separated by a blank line from the list of paths that follow for 19 readability, but when "merge" was rewritten in C, we lost it by 20 mistake. Remove the newline from "cherry-pick" to make them match 21 again. 22 23 * The command line parser choked "git cherry-pick $name" when $name can 24 be both revision name and a pathname, even though $name can never be a 25 path in the context of the command. 26 27 * The "include.path" facility in the configuration mechanism added in 28 1.7.10 forgot to interpret "~/path" and "~user/path" as it should. 29 30 * "git config --rename-section" to rename an existing section into a 31 bogus one did not check the new name. 32 33 * The "diff --no-index" codepath used limited-length buffers, risking 34 pathnames getting truncated. Update it to use the strbuf API. 35 36 * The report from "git fetch" said "new branch" even for a non branch 37 ref. 38 39 * The http-backend (the server side of the smart http transfer) used 40 to overwrite GIT_COMMITTER_NAME and GIT_COMMITTER_EMAIL with the 41 value obtained from REMOTE_USER unconditionally, making it 42 impossible for the server side site-specific customization to use 43 different identity sources to affect the names logged. It now uses 44 REMOTE_USER only as a fallback value. 45 46 * "log --graph" was not very friendly with "--stat" option and its 47 output had line breaks at wrong places. 48 49 * Octopus merge strategy did not reduce heads that are recorded in the 50 final commit correctly. 51 52 * "git push" over smart-http lost progress output a few releases ago; 53 this release resurrects it. 54 55 * The insn sheet given by "rebase -i" did not make it clear that the 56 insn lines can be re-ordered to affect the order of the commits in 57 the resulting history. 58 59 * A contrib script "rerere-train" did not work out of the box unless 60 user futzed with her $PATH. 61 62 * The i18n of error message "git stash save" was not properly done. 63 64 * "git submodule" used a sed script that some platforms mishandled. 65 66 * When using a Perl script on a system where "perl" found on user's 67 $PATH could be ancient or otherwise broken, we allow builders to 68 specify the path to a good copy of Perl with $PERL_PATH. The 69 gitweb test forgot to use that Perl when running its test. 70 71Also contains minor fixes and documentation updates.