From: merlyn@stonehenge.com (Randal L. Schwartz)
To: git@vger.kernel.org
Subject: a475e8095aeb898c1ca60673b82df97d2300cc95 broken for docs
Date: Tue, 21 Aug 2007 10:51:35 -0700 [thread overview]
Message-ID: <86odh0ojx4.fsf@blue.stonehenge.com> (raw)
xmlto -m callouts.xsl man git-rev-list.xml
xmlto: input does not validate (status 3)
/Volumes/UFS/MIRROR/git-GIT/Documentation/git-rev-list.xml:512: element literal: validity error : Element emphasis is not declared in literal list of possible children
/Volumes/UFS/MIRROR/git-GIT/Documentation/git-rev-list.xml:512: element literal: validity error : Element emphasis is not declared in literal list of possible children
/Volumes/UFS/MIRROR/git-GIT/Documentation/git-rev-list.xml:512: element literal: validity error : Element emphasis is not declared in literal list of possible children
Document /Volumes/UFS/MIRROR/git-GIT/Documentation/git-rev-list.xml does not validate
make[1]: *** [git-rev-list.1] Error 3
rm git-checkout.xml
make: *** [doc] Error 2
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next reply other threads:[~2007-08-21 17:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-21 17:51 Randal L. Schwartz [this message]
2007-08-21 21:15 ` a475e8095aeb898c1ca60673b82df97d2300cc95 broken for docs Junio C Hamano
2007-08-21 21:37 ` Randal L. Schwartz
2007-08-21 23:51 ` Junio C Hamano
2007-08-22 1:41 ` Shawn O. Pearce
2007-08-22 5:09 ` David Kastrup
2007-08-22 7:24 ` David Kastrup
2007-08-21 21:45 ` Mike Hommey
2007-08-22 8:13 ` Junio C Hamano
2007-08-22 15:02 ` Randal L. Schwartz
2007-08-22 19:45 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86odh0ojx4.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.