From: Miklos Vajna <vmiklos@frugalware.org>
To: bill lam <cbill.lam@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: quote in help code example
Date: Mon, 12 Oct 2009 21:40:16 +0200 [thread overview]
Message-ID: <20091012194016.GS23777@genesis.frugalware.org> (raw)
In-Reply-To: <20091012102926.GA3937@debian.b2j>
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
On Mon, Oct 12, 2009 at 06:29:26PM +0800, bill lam <cbill.lam@gmail.com> wrote:
> In git man, eg. git help filter-branch
> The code examples for command line or shell scripts inside .ft pairs
> use (smart?) quote instead of single quotes, like
>
> .ft C
> git filter-branch --tree-filter ´rm filename´ HEAD
> .ft
>
> Is this intentional or just some configuration problem during
> compiling.
Just a guess: do you have docbook-xsl >=1.73.0 and you did not set
ASCIIDOC_NO_ROFF?
Try rebuilding the documentation using 'make ASCIIDOC_NO_ROFF=YesPlease'.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-10-12 19:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 10:29 quote in help code example bill lam
2009-10-12 19:40 ` Miklos Vajna [this message]
2009-10-13 2:16 ` bill lam
2009-10-13 10:19 ` Miklos Vajna
2009-10-13 14:06 ` bill lam
2009-10-13 15:30 ` Miklos Vajna
2009-10-13 20:15 ` Thomas Rast
2009-10-15 12:02 ` Thomas Rast
2009-10-21 8:24 ` [PATCH] Quote ' as \(aq in manpages Thomas Rast
2009-10-21 10:38 ` Miklos Vajna
2009-10-21 18:01 ` Anders Kaseorg
2009-10-21 18:57 ` [PATCH v2] " Thomas Rast
2009-10-21 21:31 ` [PATCH] Document GNU_ROFF in Makefile Miklos Vajna
2009-10-21 22:22 ` Junio C Hamano
2009-10-21 22:51 ` Anders Kaseorg
2009-10-22 8:19 ` [PATCH v3] Quote ' as \(aq in manpages Thomas Rast
2009-10-21 21:42 ` [PATCH v2] " Anders Kaseorg
2009-10-12 21:06 ` quote in help code example 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=20091012194016.GS23777@genesis.frugalware.org \
--to=vmiklos@frugalware.org \
--cc=cbill.lam@gmail.com \
--cc=git@vger.kernel.org \
/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).