git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hugh Esco <hesco@campaignfoundations.com>
To: git@vger.kernel.org
Subject: bug report, v1.7.12.1 -- Documentation/git-rev-parse.xml:264: parser error
Date: Sun, 30 Sep 2012 04:05:21 -0400	[thread overview]
Message-ID: <20120930040521.82300f4b.hesco@campaignfoundations.com> (raw)

doing a source install of git v1.7.12.1, 
on the `make all doc` step, I get:

    XMLTO git-rev-parse.1
xmlto: input does not validate (status 1)
/usr/local/git-git-51993a4/Documentation/git-rev-parse.xml:264: parser error : Opening and ending tag mismatch: emphasis line 264 and literal
<literal><emphasis role="strong"></literal>, or <literal>[</literal>), it is tur
                                           ^
/usr/local/git-git-51993a4/Documentation/git-rev-parse.xml:264: parser error : Opening and ending tag mismatch: literal line 264 and emphasis
</literal>), it is turned into a prefix match by appending <literal>/</emphasis>
                                                                               ^
/usr/local/git-git-51993a4/Documentation/git-rev-parse.xml:277: parser error : Opening and ending tag mismatch: emphasis line 277 and literal
    character (<literal>?</literal>, <literal><emphasis role="strong"></literal>
                                                                               ^
/usr/local/git-git-51993a4/Documentation/git-rev-parse.xml:278: parser error : Opening and ending tag mismatch: literal line 278 and emphasis
        match by appending <literal>/</emphasis></literal>.
                                                ^
make[1]: *** [git-rev-parse.1] Error 1
make[1]: Leaving directory `/usr/local/git-git-51993a4/Documentation'
make: *** [doc] Error 2

-------------------------------------------
and the patch which permitted me to proceed
-------------------------------------------

264c264
> <literal></literal>, or <literal>[</literal>), it is turned into a prefix match by appending >literal>/</literal>.</simpara>
---
< <literal><emphasis role="strong"></literal>, or <literal>[</literal>), it is turned into a prefix match by appending <literal>/</emphasis></literal>.</simpara>
277,278c277,278
>         character (<literal>?</literal>, <literal></literal>, or <literal>[</literal>), it is turned into a prefix
>         match by appending <literal>/</literal>.
---
<         character (<literal>?</literal>, <literal><emphasis role="strong"></literal>, or <literal>[</literal>), it is turned into a prefix
<         match by appending <literal>/</emphasis></literal>.


-- 
Hugh Esco 
skype: hresco3_ ; 678-921-8186 x21 
http://www.CampaignFoundations.com/
Providing Application Hosting, Telephony, 
Custom Development and Consulting Services 
to Green Candidates, Green Parties and
the non profits working for a just and sustainable future.

if( $insurance->rationing() ) { $people->die(); }
if( isa_ok($self,'Troy::Davis') =~ m/^ok/) { $people->are_whole(); }

                 reply	other threads:[~2012-09-30  8:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20120930040521.82300f4b.hesco@campaignfoundations.com \
    --to=hesco@campaignfoundations.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).