Friday, November 8, 2013

Git 1.8.4.3

The latest maintenance release Git v1.8.4.3 has been tagged and is available at the usual places (see the list of public repositories). The fixes that have already merged to the 'master' branch for the upcoming Git v1.8.5 feature release are all there.

Here are the highlights, relative to the previous maintenance release v1.8.4.2:

The interaction between use of Perl in our test suite and NO_PERL has been clarified a bit.

A fast-import stream expresses a pathname with funny characters by quoting them in C style; remote-hg remote helper (in contrib/) forgot to unquote such a path.

One long-standing flaw in the pack transfer protocol used by "git clone" was that there was no way to tell the other end which branch "HEAD" points at, and the receiving end needed to guess. A new capability has been defined in the pack protocol to convey this information so that cloning from a repository with more than one branches pointing at the same commit where the HEAD is at now reliably sets the initial branch in the resulting repository.

We did not handle cases where http transport gets redirected during the authorization request (e.g. from http:// to https://).

The fall-back parsing of commit objects with broken author or committer lines were less robust than ideal in picking up the timestamps.

Bash prompting code to deal with an SVN remote as an upstream were coded in a way not supported by older Bash versions (3.x).

"git checkout topic", when there is not yet a local "topic" branch but there is a unique remote-tracking branch for a remote "topic" branch, pretended as if "git checkout -t -b topic remote/$r/topic" (for that unique remote $r) was run. This hack however was not implemented for "git checkout topic --".

Coloring around octopus merges in "log --graph" output was screwy.

We did not generate HTML version of documentation to "git subtree" in contrib/.

The synopsis section of "git unpack-objects" documentation has been clarified a bit.

An ancient How-To on serving Git repositories on an HTTP server lacked a warning that it has been mostly superseded with a more modern way.