From: Hugh Esco <hesco@campaignfoundations.com>
To: git@vger.kernel.org
Subject: bug report, v1.7.12.1 -- Documentation/git-check-ref-format.xml:162: parser error
Date: Sun, 30 Sep 2012 03:15:00 -0400 [thread overview]
Message-ID: <20120930031500.997b6bfb.hesco@campaignfoundations.com> (raw)
doing a source install of git v1.7.12.1,
on the `make all doc` step, I get:
xmlto: input does not validate (status 1)
/usr/local/git-git-51993a4/Documentation/git-check-ref-format.xml:162: parser error : Opening and ending tag mismatch: emphasis line 162 and literal
me> is allowed to contain a single <literal><emphasis role="strong"></literal
^
/usr/local/git-git-51993a4/Documentation/git-check-ref-format.xml:164: parser error : Opening and ending tag mismatch: literal line 164 and emphasis
<literal>foo/</emphasis>/bar</literal> but not <literal>foo/bar*</litera
^
make[1]: *** [git-check-ref-format.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
-------------------------------------------
162c162
< enabled, <refname> is allowed to contain a single <literal></literal>
---
> enabled, <refname> is allowed to contain a single <literal><emphasis role="strong"></literal>
164c164
< <literal>foo/bar</literal> but not <literal>foo/bar*</literal>).
---
> <literal>foo/</emphasis>/bar</literal> but not <literal>foo/bar*</literal>).
-------------------------------------------
Next issue shows up in:
Documentation/git-config.xml
details coming under separate cover.
--
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 7:16 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=20120930031500.997b6bfb.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).