linux-kernel - Re: [ANNOUNCE] Git 1.7.7.rc3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 26 Sep 2011 10:48:56 -0700 (PDT)
From:	Jakub Narebski <jnareb@...il.com>
To:	Ævar Arnfjörð Bjarmason <avarab@...il.com>
Cc:	Junio C Hamano <gitster@...ox.com>, git@...r.kernel.org,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [ANNOUNCE] Git 1.7.7.rc3

Ævar Arnfjörð Bjarmason wrote:
> On Sat, Sep 24, 2011 at 01:41, Junio C Hamano <gitster@...ox.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/