1Git v1.7.9.3 Release Notes 2========================== 3 4Fixes since v1.7.9.2 5-------------------- 6 7 * "git p4" (in contrib/) submit the changes to a wrong place when the 8 "--use-client-spec" option is set. 9 10 * The config.mak.autogen generated by optional autoconf support tried 11 to link the binary with -lintl even when libintl.h is missing from 12 the system. 13 14 * When the filter driver exits before reading the content before the 15 main git process writes the contents to be filtered to the pipe to 16 it, the latter could be killed with SIGPIPE instead of ignoring 17 such an event as an error. 18 19 * "git add --refresh <pathspec>" used to warn about unmerged paths 20 outside the given pathspec. 21 22 * The bulk check-in codepath in "git add" streamed contents that 23 needs smudge/clean filters without running them, instead of punting 24 and delegating to the codepath to run filters after slurping 25 everything to core. 26 27 * "git branch --with $that" assumed incorrectly that the user will never 28 ask the question with nonsense value in $that. 29 30 * "git bundle create" produced a corrupt bundle file upon seeing 31 commits with excessively long subject line. 32 33 * When a remote helper exits before reading the blank line from the 34 main git process to signal the end of commands, the latter could be 35 killed with SIGPIPE. Instead we should ignore such event as a 36 non-error. 37 38 * The commit log template given with "git merge --edit" did not have 39 a short instructive text like what "git commit" gives. 40 41 * "git rev-list --verify-objects -q" omitted the extra verification 42 it needs to do over "git rev-list --objects -q" by mistake. 43 44 * "gitweb" used to drop warnings in the log file when "heads" view is 45 accessed in a repository whose HEAD does not point at a valid 46 branch. 47 48 * An invalid regular expression pattern given by an end user made 49 "gitweb" to return garbled response. 50 51Also contains minor fixes and documentation updates.