1Git v1.8.4.3 Release Notes 2======================== 3 4Fixes since v1.8.4.2 5-------------------- 6 7 * The interaction between use of Perl in our test suite and NO_PERL 8 has been clarified a bit. 9 10 * A fast-import stream expresses a pathname with funny characters by 11 quoting them in C style; remote-hg remote helper (in contrib/) 12 forgot to unquote such a path. 13 14 * One long-standing flaw in the pack transfer protocol used by "git 15 clone" was that there was no way to tell the other end which branch 16 "HEAD" points at, and the receiving end needed to guess. A new 17 capability has been defined in the pack protocol to convey this 18 information so that cloning from a repository with more than one 19 branches pointing at the same commit where the HEAD is at now 20 reliably sets the initial branch in the resulting repository. 21 22 * We did not handle cases where http transport gets redirected during 23 the authorization request (e.g. from http:// to https://). 24 25 * "git rev-list --objects ^v1.0^ v1.0" gave v1.0 tag itself in the 26 output, but "git rev-list --objects v1.0^..v1.0" did not. 27 28 * The fall-back parsing of commit objects with broken author or 29 committer lines were less robust than ideal in picking up the 30 timestamps. 31 32 * Bash prompting code to deal with an SVN remote as an upstream 33 were coded in a way not supported by older Bash versions (3.x). 34 35 * "git checkout topic", when there is not yet a local "topic" branch 36 but there is a unique remote-tracking branch for a remote "topic" 37 branch, pretended as if "git checkout -t -b topic remote/$r/topic" 38 (for that unique remote $r) was run. This hack however was not 39 implemented for "git checkout topic --". 40 41 * Coloring around octopus merges in "log --graph" output was screwy. 42 43 * We did not generate HTML version of documentation to "git subtree" 44 in contrib/. 45 46 * The synopsis section of "git unpack-objects" documentation has been 47 clarified a bit. 48 49 * An ancient How-To on serving Git repositories on an HTTP server 50 lacked a warning that it has been mostly superseded with more 51 modern way. 52 53Also contains a handful of trivial code clean-ups, documentation 54updates, updates to the test suite, etc.