From: Jakub Narebski <jnareb@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git 1.7.7.rc3
Date: Mon, 26 Sep 2011 10:48:56 -0700 (PDT) [thread overview]
Message-ID: <m3bou7p542.fsf@localhost.localdomain> (raw)
In-Reply-To: <CACBZZX77ZhdS1cyiYpjJcuvSnJsv15FUumPWeZOcwh_b41c2FQ@mail.gmail.com>
Æ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
prev parent reply other threads:[~2011-09-26 17:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 23:41 [ANNOUNCE] Git 1.7.7.rc3 Junio C Hamano
2011-09-26 12:47 ` Ævar Arnfjörð Bjarmason
2011-09-26 17:48 ` Jakub Narebski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3bou7p542.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox