From: Thomas Rast <trast@inf.ethz.ch>
To: Jeff King <peff@peff.net>
Cc: "Carlos Martín Nieto" <cmn@elego.de>, git@vger.kernel.org
Subject: Re: [PATCH] Documentation: use {asterisk} in rev-list-options.txt when needed
Date: Wed, 29 Feb 2012 00:03:53 +0100 [thread overview]
Message-ID: <87hayar25i.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <20120228194551.GC11725@sigill.intra.peff.net> (Jeff King's message of "Tue, 28 Feb 2012 14:45:51 -0500")
Jeff King <peff@peff.net> writes:
> Anyway, that is not a problem with your patch. :) I confirmed that the
> bug happens in my version of the toolchain, and your fix works (I also
> tried using `*`, but backtick does not suppress markup.
Actually it would, if it weren't for our use of '-a no-inline-literal'.
Which we are using because the "backticks do not interpret {stuff}"
feature was introduced in a backwards-incompatible way in asciidoc
8.4.1, see 71c020c (Disable asciidoc 8.4.1+ semantics for `{plus}` and
friends, 2009-07-25).
Some googling tells me the distros are currently at
openSuSE 8.4.5 (local)
Debian (stable) 8.5.2 packages.debian.org
Fedora 8.4.5 admin.fedoraproject.org/pkgdb/
(but I can't discern whether it's actually in there...)
Arch 8.6.6 www.archlinux.org/packages/
Ubuntu 11.10 8.6.4 packages.ubuntu.com
so perhaps the time has come to remove that switch?
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2012-02-28 23:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 15:35 [PATCH] Documentation: use {asterisk} in rev-list-options.txt when needed Carlos Martín Nieto
2012-02-28 19:38 ` Junio C Hamano
2012-02-28 19:45 ` Jeff King
2012-02-28 20:20 ` Carlos Martín Nieto
2012-02-28 21:18 ` Junio C Hamano
2012-02-28 23:03 ` Thomas Rast [this message]
2012-02-29 21:38 ` Jeff King
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=87hayar25i.fsf@thomas.inf.ethz.ch \
--to=trast@inf.ethz.ch \
--cc=cmn@elego.de \
--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).