From: Thomas Rast <trast@student.ethz.ch>
To: Saikiran Madugula <hummerbliss@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation: Fix build failure of docs.
Date: Tue, 28 Jul 2009 18:02:21 +0200 [thread overview]
Message-ID: <200907281802.23171.trast@student.ethz.ch> (raw)
In-Reply-To: <4A6F1B89.9080202@gmail.com>
Saikiran Madugula wrote:
> This patch fixes the build failure due to what seems to be extraneous
> characters, "+++" in the git-filter-branch.txt file.
[...]
> ASCIIDOC git-filter-branch.xml
> XMLTO git-filter-branch.1
> xmlto: input does not validate (status 1)
> /home/bobthe/git.kernel.org/git/Documentation/git-filter-branch.xml:435:
> parser error : PCDATA invalid Char value 7
> Clone it with <literal>git clone +++0+++</literal>. The clone
NAK. Presumably you are using an asciidoc 8.x? Please check if
saying
make ASCIIDOC8=Yes man
fixes the problem. Read the comments in Documentation/Makefile for
advice on what precise combination of options you should use. Also,
if you do not want to actually work on docs
make quick-install-man
is a much less painful way to get manpages (in this case, from Junio's
'man' branch that has preformatted manpages for 'master').
I put the +++ in there to stop the version I used at the time from
rendering the closing backtick as part of the URL and garbling the
entire paragraph in the process. To be precise, with asciidoc 8.2.7
and without the +++ I get
Clone it with <tt>git clone <a href="file:///path/to/repo</tt">file:///path/to/repo</tt</a>>.
in the HTML output. Note the nested tags. (With asciidoc 8.4.5 the
problem appears to be fixed.)
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2009-07-28 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 15:38 [PATCH] Documentation: Fix build failure of docs Saikiran Madugula
2009-07-28 16:02 ` Thomas Rast [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-07-28 16:39 Saikiran Madugula
2009-07-28 18:03 ` Michael J Gruber
2009-07-29 9:09 ` Saikiran Madugula
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=200907281802.23171.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=hummerbliss@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).