From: Francis Daly <francis@daoine.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Tweak asciidoc output to work with broken docbook-xsl
Date: Mon, 6 Mar 2006 01:09:07 +0000 [thread overview]
Message-ID: <20060306010907.GA22105@craic.sysops.org> (raw)
In-Reply-To: <7vr75gcs20.fsf@assigned-by-dhcp.cox.net>
On Sun, Mar 05, 2006 at 04:53:11PM -0800, Junio C Hamano wrote:
> Francis Daly <francis@daoine.org> writes:
> > asciidoc by default converts "listingblock" to "<screen>". This change
> > causes asciidoc in git to convert "listingblock" to "<literallayout>", which
> > both old and new docbook-xsl handle correctly.
>
> Have you tested html generation side? With 1.68 I seem to be
> getting an disaster.
Oh how stupid of me.
Yes, of course you're right. The backend matters.
Clearly, I don't read the html pages; and no-one (with old stylesheets)
reads the man pages ;-)
Thanks,
f
--
Francis Daly francis@daoine.org
prev parent reply other threads:[~2006-03-06 1:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-05 23:13 [PATCH] Tweak asciidoc output to work with broken docbook-xsl Francis Daly
2006-03-06 0:53 ` Junio C Hamano
2006-03-06 1:09 ` Francis Daly [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=20060306010907.GA22105@craic.sysops.org \
--to=francis@daoine.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).