From: Hugh Esco <hesco@campaignfoundations.com>
To: git@vger.kernel.org
Subject: bug report, v1.7.12.1 -- user-manual.xml:3739: parser error
Date: Sun, 30 Sep 2012 02:59:32 -0400 [thread overview]
Message-ID: <20120930025932.06fa1894.hesco@campaignfoundations.com> (raw)
Apologies for duplicates.
Perhaps the patch below will earn me a small bit of leeway.
-- Hugh Esco
doing a source install of git v1.7.12.1,
on the `make all doc` step, I get:
user-manual.xml:3739: parser error : Opening and ending tag mismatch: emphasis line 3739 and literal
char <emphasis role="strong"></literal>, but is actually expected to be a poin
^
user-manual.xml:3741: parser error : Opening and ending tag mismatch: literal line 3741 and emphasis
mit. Note that whenever a SHA-1 is passed as <literal>unsigned char </emphasis>
^
unable to parse user-manual.xml
make[1]: *** [user-manual.html] Error 6
make[1]: Leaving directory `/usr/local/git-git-51993a4/Documentation'
make: *** [doc] Error 2
----------------------------------------------
and the patch which permitted me to proceed
although it removes a malformed <emphasis> tag
----------------------------------------------
3739c3739
< char </literal>, but is actually expected to be a pointer to <literal>unsigned
---
> char <emphasis role="strong"></literal>, but is actually expected to be a pointer to <literal>unsigned
3741c3741
< commit. Note that whenever a SHA-1 is passed as <literal>unsigned char </literal>, it
---
> commit. Note that whenever a SHA-1 is passed as <literal>unsigned char </emphasis></literal>, it
----------------------------------------------
I've encountered another issue with:
Documentation/git-bundle.xml
I will post the details in a distinct message,
perhaps even with another patch if I can sort this out.
--
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(); }
next reply other threads:[~2012-09-30 7:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-30 6:59 Hugh Esco [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-30 6:15 bug report, v1.7.12.1 -- user-manual.xml:3739: parser error Hugh Esco
2012-09-30 7:04 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120930025932.06fa1894.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).