From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Chris Johnsen <chris_johnsen@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 3/8] Documentation: rename docbook-xsl-172 attribute to git-asciidoc-no-roff
Date: Thu, 26 Mar 2009 09:47:53 -0700 [thread overview]
Message-ID: <7vocvop6x2.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20090326094322.GB14292@coredump.intra.peff.net> (Jeff King's message of "Thu, 26 Mar 2009 05:43:22 -0400")
Jeff King <peff@peff.net> writes:
> On Tue, Mar 24, 2009 at 02:48:52PM -0500, Chris Johnsen wrote:
>
>> I am not opposed to providing more version-specific controls, but I am not
>> sure which versions are important enough to justify their own variables.
>> Are you indicating that 1.73 is important enough because it was a "return
>> to sanity" after 1.72?
>
> No, mainly because it is what is shipped in the last version of Debian,
> which means it is a major enough version that there will be a lot of
> people using it.
>
> But let's just start with adding the tweakable knobs (which your series
> is already doing), and see in what ways they need to be tweaked for
> popular platforms before going overboard.
When I was trying out the series yesterday, I was wondering if this is
something we can autodetect.
Output from "asciidoc --version" is easily machine parsable for giving
asciidoc7compatible aka ASCIIDOC8, but I couldn't come up with anything
simpler than probing a few hardcoded paths under /usr/share/sgml; that
approach is unacceptable because would not work if your stylesheets are in
somewhere we do not know about. Ideally, we should be able to ask the
tools we invoke (e.g. xmlto) to get that information.
next prev parent reply other threads:[~2009-03-26 16:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 8:04 [PATCH 0/8] Documentation: XSLT/asciidoc.conf cleanup; tty literals Chris Johnsen
2009-03-24 8:04 ` [PATCH 1/8] Documentation: move callouts.xsl to manpage-{base,normal}.xsl Chris Johnsen
2009-03-24 8:51 ` Jeff King
2009-03-24 19:36 ` Chris Johnsen
2009-03-26 9:40 ` Jeff King
2009-03-24 8:04 ` [PATCH 2/8] Documentation: use parametrized manpage-base.xsl with manpage-{1.72,normal}.xsl Chris Johnsen
2009-03-24 8:57 ` Jeff King
2009-03-24 19:42 ` Chris Johnsen
2009-03-24 8:04 ` [PATCH 3/8] Documentation: rename docbook-xsl-172 attribute to git-asciidoc-no-roff Chris Johnsen
2009-03-24 9:04 ` Jeff King
2009-03-24 19:48 ` Chris Johnsen
2009-03-26 9:43 ` Jeff King
2009-03-26 16:47 ` Junio C Hamano [this message]
2009-03-26 18:49 ` Michael J Gruber
2009-03-24 8:04 ` [PATCH 4/8] Documentation: move quieting params into manpage-base.xsl Chris Johnsen
2009-03-24 9:18 ` Jeff King
2009-03-25 4:21 ` [PATCH 1/2] Documentation/Makefile: make most operations "quiet" Chris Johnsen
2009-03-25 4:21 ` [PATCH 2/2] Documentation/Makefile: break up texi pipeline Chris Johnsen
2009-03-25 4:28 ` [PATCH 1/2] Documentation/Makefile: make most operations "quiet" Jeff King
2009-03-25 9:55 ` Chris Johnsen
2009-03-24 8:04 ` [PATCH 5/8] Documentation: move "spurious .sp" code into manpage-base.xsl Chris Johnsen
2009-03-24 8:04 ` [PATCH 6/8] Documentation: asciidoc.conf: always use <literallayout> for [blocktext] Chris Johnsen
2009-03-24 8:04 ` [PATCH 7/8] Documentation: asciidoc.conf: fix verse block with block titles Chris Johnsen
2009-03-24 8:04 ` [PATCH 8/8] Documentation: option to render literal text as bold for manpages Chris Johnsen
2009-03-26 8:59 ` [PATCH 0/8] Documentation: XSLT/asciidoc.conf cleanup; tty literals 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=7vocvop6x2.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=chris_johnsen@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.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).