From: Jeff King <peff@peff.net>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org, Steven Grimm <koreth@midwinter.com>,
Brian Gernhardt <benji@silverinsanity.com>
Subject: Re: [PATCH 2/2] Documentation/git-gc: improve description of --auto
Date: Thu, 18 Oct 2007 22:38:50 -0400 [thread overview]
Message-ID: <20071019023850.GD8298@coredump.intra.peff.net> (raw)
In-Reply-To: <20071019022909.GZ14735@spearce.org>
On Thu, Oct 18, 2007 at 10:29:09PM -0400, Shawn O. Pearce wrote:
> I personally prefer to read commands in the source as `foo` and
> feel that asciidoc should just format it correctly for the backend.
> If it isn't then we should try to work with the asciidoc folks to
> get it right...
I am hunting this down right now. asciidoc _does_ generate
XML <literal>foo</literal> for `foo`, but it looks like docbook is
throwing that away when converting to manpages. Hopefully there is an
easy tweak...
-Peff
next prev parent reply other threads:[~2007-10-19 2:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 2:05 [PATCH 2/2] Documentation/git-gc: improve description of --auto Jeff King
2007-10-19 2:29 ` Shawn O. Pearce
2007-10-19 2:38 ` Jeff King [this message]
2007-10-19 4:45 ` 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=20071019023850.GD8298@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=benji@silverinsanity.com \
--cc=git@vger.kernel.org \
--cc=koreth@midwinter.com \
--cc=spearce@spearce.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.