From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-sh-i18n--envsubst: add SYNOPSIS section to the documentation
Date: Mon, 30 May 2011 01:09:41 -0700 [thread overview]
Message-ID: <7vaae4obi2.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1306666835-8978-1-git-send-email-avarab@gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Sun, 29 May 2011 11:00:35 +0000")
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> Not having a SYNOPSIS section caused the "doc" target to fail on
> Centos 5.5 with asciidoc 8.2.5, while building with 8.6.4 on Debian
> works just fine.
So does FC13 and FC15, both of which has 8.4.5.
Will queue; thanks.
prev parent reply other threads:[~2011-05-30 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-28 11:40 Documentation doesn't build anymore on old asciidoc due to i18n series Ævar Arnfjörð Bjarmason
2011-05-29 11:00 ` [PATCH] git-sh-i18n--envsubst: add SYNOPSIS section to the documentation Ævar Arnfjörð Bjarmason
2011-05-30 8:09 ` Junio C Hamano [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=7vaae4obi2.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=git@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;
as well as URLs for NNTP newsgroup(s).