From: Michael J Gruber <git@drmicha.warpmail.net>
To: Tom Holaday <tlholaday@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git doc build failure on OS X 10.5.6 (Leopard) during xmlto phase
Date: Wed, 11 Mar 2009 15:43:06 +0100 [thread overview]
Message-ID: <49B7CDFA.30006@drmicha.warpmail.net> (raw)
In-Reply-To: <5e68abd90903110721o414283a4te188b58e0e4df8ad@mail.gmail.com>
Tom Holaday venit, vidit, dixit 11.03.2009 15:21:
> Hello,
>
> On OS X 10.5.6 (Leopard), the command ...
>
> xmlto -m callouts.xsl man git-filter-branch.xml
>
> ... terminates with these errors:
>
> xmlto: input does not validate (status 1)
> /git-1.6.2/Documentation/git-filter-branch.xml:431: parser error :
> PCDATA invalid Char value 7
> Clone it with <literal>git clone +++0+++</literal>. The clone
> ^
> /git-1.6.2/Documentation/git-filter-branch.xml:431: parser error :
> PCDATA invalid Char value 7
> Clone it with <literal>git clone +++0+++</literal>. The clone
That means that the xml file is incorrect already, which means it's an
asciidoc problem. What's your asciidoc version?
> ^
> make[1]: *** [git-filter-branch.1] Error 1
> make: *** [doc] Error 2
>
> What issue-tracker, if any, would be appropriate for this?
You should send a note to the mailing list ;)
Michael
next prev parent reply other threads:[~2009-03-11 14:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 14:21 git doc build failure on OS X 10.5.6 (Leopard) during xmlto phase Tom Holaday
2009-03-11 14:43 ` Michael J Gruber [this message]
2009-03-11 15:12 ` Jay Soffian
2009-03-11 15:39 ` Jay Soffian
2009-03-11 15:49 ` Jay Soffian
2009-03-11 16:27 ` Michael J Gruber
2009-03-11 20:12 ` Alejandro Riveira
2009-03-12 11:17 ` Michael J Gruber
2009-03-12 14:02 ` Alejandro Riveira Fernández
2009-03-12 17:09 ` Todd Zullinger
2009-03-13 10:29 ` Michael J Gruber
2009-03-13 16:18 ` Jay Soffian
2009-03-13 17:06 ` Michael J Gruber
2009-03-31 20:17 ` byrnejb
2009-03-31 20:56 ` byrnejb
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=49B7CDFA.30006@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=tlholaday@gmail.com \
/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).