From: "Carlos Martín Nieto" <cmn@elego.de>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation: use {asterisk} in rev-list-options.txt when needed
Date: Tue, 28 Feb 2012 21:20:23 +0100 [thread overview]
Message-ID: <1330460423.691.15.camel@centaur.lab.cmartin.tk> (raw)
In-Reply-To: <20120228194551.GC11725@sigill.intra.peff.net>
[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]
On Tue, 2012-02-28 at 14:45 -0500, Jeff King wrote:
> On Tue, Feb 28, 2012 at 04:35:48PM +0100, Carlos Martín Nieto wrote:
>
> > Text between to '*' is emphasized in AsciiDoc which made the
>
> s/to/two/
Oops. Thanks. Can you squash that in, Junio?
>
> > glob-related explanations in rev-list-options.txt very confusing, as
> > the rendered text would be missing two asterisks and the text between
> > them would be emphasized instead.
> >
> > Use '{asterisk}' where needed to make them show up as asterisks in the
> > rendered text.
> > [...]
> > - '*', or '[', '/*' at the end is implied.
> > + '{asterisk}', or '[', '/{asterisk}' at the end is implied.
>
> Ugh. I hate asciidoc more with each passing year. Readable source
> documents are such a wonderful idea, but the markup makes it less and
> less readable as we accumulate fixes like this. I wonder if this has
> always been a bug, or something that appeared in more recent versions of
> the toolchain.
The generated documentation in the 'html' branch shows the wrong
formatting as well even for 1.7.0 when the --glob feature and its
explanation was first introduced. So either nobody reads the
documentation or very few people actually care about --glob and use the
--remotes and friends, where that part of the explanation isn't that
interesting.
cmn
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2012-02-28 20:20 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 [this message]
2012-02-28 21:18 ` Junio C Hamano
2012-02-28 23:03 ` Thomas Rast
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=1330460423.691.15.camel@centaur.lab.cmartin.tk \
--to=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).