[ANNOUNCE] Git 1.7.6.4

The latest maintenance release Git 1.7.6.4 is available but not at the usual places.

The release tarballs are found at:

    http://code.google.com/p/git-core/downloads/list

and their SHA-1 checksums are:

df91e2c32d6097ab1c9d0edc56dd8cecb4e9b686 git-1.7.6.4.tar.gz 6abd985e24b6585284cef7fae2e3046ba9201356 git-htmldocs-1.7.6.4.tar.gz c6f6d92f4005a7eccaf89e851c45768c18f7e65a git-manpages-1.7.6.4.tar.gz

Also the following public repositories all have a copy of the v1.7.6.4 tag and the maint branch that the tag points at:

        url = git://repo.or.cz/alt-git.git
        url = https://code.google.com/p/git-core/
        url = git://git.sourceforge.jp/gitroot/git-core/git.git
        url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core
        url = https://github.com/gitster/git

Git v1.7.6.4 Release Notes ==========================

Fixes since v1.7.6.3 --------------------

 * The error reporting logic of "git am" when the command is fed a file
   whose mail-storage format is unknown was fixed.

 * "git branch --set-upstream @{-1} foo" did not expand @{-1} correctly.

 * "git check-ref-format --print" used to parrot a candidate string that
   began with a slash (e.g. /refs/heads/master) without stripping it, to make
   the result a suitably normalized string the caller can append to "$GIT_DIR/".

 * "git clone" failed to clone locally from a ".git" file that itself
   is not a directory but is a pointer to one.

 * "git clone" from a local repository that borrows from another
   object store using a relative path in its objects/info/alternates
   file did not adjust the alternates in the resulting repository.

 * "git describe --dirty" did not refresh the index before checking the
   state of the working tree files.

 * "git ls-files ../$path" that is run from a subdirectory reported errors
   incorrectly when there is no such path that matches the given pathspec.

 * "git mergetool" could loop forever prompting when nothing can be read
   from the standard input.

Also contains minor fixes and documentation updates.

On Sep 23, 2011, at 19:37 , Junio C Hamano wrote:

When building 1.7.6.4 on my RHEL 4 system, it failed t1402-check-ref-format.sh:

 not ok - 19 ref name 'heads/foo' is not valid

I bisected and found that commit f3738c1ce9193a4bf45ba1a3ea67d0cf32da0257 introduced the issue. 

The test

 invalid_ref "$(printf 'heads/foo\177')"

was added to t1402-check-ref-format.sh. However sh on my RHEL 4 system does not handle the DEL (\177) character well in double quoted strings.

sh-3.00$ echo $(printf 'hello\177') | hexdump -C 00000000 68 65 6c 6c 6f 7f 0a |hello..| 00000007 sh-3.00$ echo "$(printf 'hello\177')" | hexdump -C 00000000 68 65 6c 6c 6f 0a |hello.| 00000006

The double quotes cause the DEL (\177) character to be discarded.

Can this test be rewritten to avoid this apparent bug in sh on RHEL 4?

BJ Hargrave <bj@bjhargrave.com> writes:

For older distros, I would prefer a workaround patch first tested by distro packaging people and then upstreamed.

Thanks.

On Fri, Sep 23, 2011 at 04:37:53PM -0700,  Junio C Hamano wrote:

Can you please upload the manpages and htmldocs tarballs to code.google.com downloads? We use them in packaging on Gentoo for users that want the docs without all of the documentation build chain.

(For 1.7.7.rc* too please).