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/gitcredentials.xml:180: parser error
Date: Sun, 30 Sep 2012 04:27:31 -0400	[thread overview]
Message-ID: <20120930042731.d8e2086d.hesco@campaignfoundations.com> (raw)

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

    XMLTO gitcredentials.7
xmlto: input does not validate (status 1)
/usr/local/git-git-51993a4/Documentation/gitcredentials.xml:180: parser error : Opening and ending tag mismatch: emphasis line 180 and literal
<literal>credential.<emphasis role="strong"></literal> (which applies to all cre
                                                      ^
/usr/local/git-git-51993a4/Documentation/gitcredentials.xml:181: parser error : Opening and ending tag mismatch: literal line 181 and emphasis
<literal>credential.&lt;url&gt;.</emphasis></literal>, where &lt;url&gt; matches
                                           ^
make[1]: *** [gitcredentials.7] Error 1
make[1]: Leaving directory `/usr/local/git-git-51993a4/Documentation'
make: *** [doc] Error 2
pbx:/usr/local/git-git-51993a4# diff Documentation/gitcore-tutorial.xml ~hesco/gitcore-tutorial.xml 
824c824
< (notice the asterisk <literal></literal> character), and the first column for
---
> (notice the asterisk <literal><emphasis role="strong"></literal> character), and the first column for
828c828
< All of them have non blank characters in the first column (<literal></literal>
---
> All of them have non blank characters in the first column (<literal></emphasis></literal>
1263c1263
< <note><simpara>You will see two files, <literal>pack-.pack</literal> and <literal>pack-.idx</literal>,
---
> <note><simpara>You will see two files, <literal>pack-<emphasis role="strong">.pack</literal> and <literal>pack-</emphasis>.idx</literal>,

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

180,181c180,181
< <literal>credential.</literal> (which applies to all credentials), or
< <literal>credential.&lt;url&gt;.</literal>, where &lt;url&gt; matches the context as described
---
> <literal>credential.<emphasis role="strong"></literal> (which applies to all credentials), or
> <literal>credential.&lt;url&gt;.</emphasis></literal>, where &lt;url&gt; matches the context as described

And with the resolution of this bug, 
the `make doc all` completed without further error.  

Not sure if my version of the xml parser does not recognize 
the emphasis tag, although many of these involved overlapping 
tags and sometimes I saw tags which wrapped literally nothing 
at all.  Have no idea what that might have been about.  

-- 
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:28 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=20120930042731.d8e2086d.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).