[ANNOUNCE] Git 1.7.7.rc3

[ANNOUNCE] Git 1.7.7.rc3

[Junio C Hamano]

A release candidate Git 1.7.7.rc3 is available for testing but not at the
usual places.

The tarball is found at:

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

and its SHA-1 checksum is:

c6ba05a833cab49dd66dd1e252306e187effbf2b  git-1.7.7.rc3.tar.gz

Also the following public repositories all have a copy of the v1.7.7-rc3
tag and the master 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

I had to make a quick fix for a recent regression directly on master, and
I would like to cook it for a few days, so the final has to wait til mid
next week.

Until then please help testing to find other regressions.

----------------------------------------------------------------

Changes since v1.7.7-rc2 are as follows:

Allan Caffee (1):
      describe: Refresh the index when run with --dirty

Jay Soffian (1):
      git-mergetool: check return value from read

Jeff King (1):
      t4014: clean up format.thread config after each test

Junio C Hamano (3):
      Git 1.7.6.4
      merge-recursive: Do not look at working tree during a virtual ancestor merge
      Git 1.7.7-rc3

Re: [ANNOUNCE] Git 1.7.7.rc3

[Ævar Arnfjörð Bjarmason]

On Sat, Sep 24, 2011 at 01:41, Junio C Hamano <gitster@pobox.com> wrote:

> Also the following public repositories all have a copy of the v1.7.7-rc3
> tag and the master branch that the tag points at:

The 1.7.7-rc* series still doesn't compile on older Red Hat machines
because 4c1be38b4a236403a329187acb70591a7fd92150 hasn't been included
in it.

Could you please include that in the final 1.7.7? It would be a PITA
to have to work around that.

Re: [ANNOUNCE] Git 1.7.7.rc3

[Jakub Narebski]

Ævar Arnfjörð Bjarmason wrote:
> On Sat, Sep 24, 2011 at 01:41, Junio C Hamano <gitster@pobox.com> wrote:
> 
> > Also the following public repositories all have a copy of the v1.7.7-rc3
> > tag and the master branch that the tag points at:
> 
> The 1.7.7-rc* series still doesn't compile on older Red Hat machines
> because 4c1be38b4a236403a329187acb70591a7fd92150 hasn't been included
> in it.
> 
> Could you please include that in the final 1.7.7? It would be a PITA
> to have to work around that.

It looks like I was too optimistic in

  "Re: What's cooking in git.git (Sep 2011, #06; Wed, 21)"
  http://thread.gmane.org/gmane.comp.version-control.git/181885/focus=181935

JN> Yes, that is what I mean... but that it is only because I use old
JN> version of asciidoc (7.1.2).
JN>  
JN> "make doc" (which is part of "make rpm") fails on my box with
JN> 
JN>       ASCIIDOC gitnamespaces.html
JN>   ERROR: gitnamespaces.txt: line 9: second section must be named SYNOPSIS
JN>   make[1]: *** [gitnamespaces.html] Error 1
JN> 
JN> > If the reason the documentation fix for "master" is needed is because a
JN> > new feature scheduled for the upcoming release has broken documentation,
JN> > then wouldn't we need the fix before the release, whether you are working
JN> > on your patch or not? How can it be not urgent if that is the case?
JN> > 
JN> > On my boxes with recent Debian, Ubuntu, and F14, I am not suffering from
JN> > the lack of the workaround, but if distros need the workaround, then the
JN> > time to apply it is now, not post release.
JN> 
JN> I don't think _modern_ distributions need this workaround... asciidoc 8.4.5
JN> which fixed the issue with "Synopsis" section was released 2009-05-24:
JN> 
JN> http://www.methods.co.nz/asciidoc/CHANGELOG.html
JN> 
JN>   Version 8.4.5 (2009-05-24)
JN>   --------------------------
JN>   Additions and changes
JN>   ~~~~~~~~~~~~~~~~~~~~~
JN> 
JN>     * Added manpage "Name" and "Synopsis" section title customization to
JN>       languages configuration files.
JN>     * "Synopsis" manpage section no longer mandatory.
JN>   [...]

-- 
Jakub Narębski