From: Junio C Hamano <junkio@cox.net>
To: "Horst H. von Brand" <vonbrand@inf.utfsm.cl>
Cc: git@vger.kernel.org
Subject: Re: Generating docu in 1.4.3.3.g01929
Date: Fri, 27 Oct 2006 14:34:55 -0700 [thread overview]
Message-ID: <7vodrxe934.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200610271726.k9RHQr0F024712@laptop13.inf.utfsm.cl> (Horst H. von Brand's message of "Fri, 27 Oct 2006 14:26:53 -0300")
"Horst H. von Brand" <vonbrand@inf.utfsm.cl> writes:
> I'm getting lots of these after today's pull:
>
> asciidoc -b docbook -d manpage -f asciidoc.conf git-daemon.txt
> xmlto -m callouts.xsl man git-daemon.xml
> error : unterminated entity reference
> error : unterminated entity reference
> error : unterminated entity reference ...
> error : unterminated entity reference
> error : unterminated entity reference
> Writing git-daemon.1 for refentry
Is it only with git-daemon.txt (as opposed to other files like
git-cat-file.txt), is it only with generating git-daemon.1 (as
opposed to generating git-daemon.html), and is it only with
today's pull (as opposed to 1.4.3.3)?
The point I am getting at is if it is only for you and if so
we might want to pinpoint where the breakage is.
I do not see it with my xmlto and asciidoc combination, either
on FC6 nor on Debian testing.
prev parent reply other threads:[~2006-10-27 21:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-27 17:26 Generating docu in 1.4.3.3.g01929 Horst H. von Brand
2006-10-27 19:44 ` Sean
[not found] ` <20061027154433.da9b29d7.seanlkml@sympatico.ca>
2006-10-27 23:12 ` Horst H. von Brand
2006-10-28 4:24 ` Sean
2006-10-28 5:45 ` Junio C Hamano
2006-10-28 6:07 ` Sean
2006-10-28 19:04 ` Junio C Hamano
2006-10-28 19:13 ` Sean
2006-10-28 19:22 ` Junio C Hamano
2006-10-29 19:03 ` Horst H. von Brand
2006-10-27 21:34 ` Junio C Hamano [this message]
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=7vodrxe934.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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.