From: Sam Vilain <sam@vilain.net>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] Documentation/gitmodules: fix asciidoc
Date: Fri, 15 Jun 2007 15:53:40 +1200 [thread overview]
Message-ID: <46720D44.2040409@vilain.net> (raw)
In-Reply-To: <20070615034915.GE18491@spearce.org>
Shawn O. Pearce wrote:
> Sam Vilain <sam.vilain@catalyst.net.nz> wrote:
>
>> ---
>> I was getting documentation build errors without this
>>
>
> Yea, I got doc build errors today too from `next` but did not have
> time to track down what was causing them. Something about the XML
> not matching the DocBook DTD.
Yep, the synopsis section did not have enough in it to satisfy the
requirements of asciidoc, so it generated an empty <refsynopsisinfo>
section which doesn't match the DocBook 4.2 DTD.
Perhaps there is another solution by fixing the asciidoc.conf... but
looks like voodoo to me :)
Sam.
next prev parent reply other threads:[~2007-06-15 3:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 3:42 [PATCH] Documentation/gitmodules: fix asciidoc Sam Vilain
2007-06-15 3:49 ` Shawn O. Pearce
2007-06-15 3:53 ` Sam Vilain [this message]
2007-06-15 7:11 ` Lars Hjemli
2007-06-16 1:53 ` Sam Vilain
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=46720D44.2040409@vilain.net \
--to=sam@vilain.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=spearce@spearce.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).