From: Junio C Hamano <gitster@pobox.com>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: David Kastrup <dak@gnu.org>, git@vger.kernel.org
Subject: Re: Trouble generating info documentation
Date: Wed, 02 Jan 2008 10:59:37 -0800 [thread overview]
Message-ID: <7vsl1gvysm.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 20080102170556.GD29972@genesis.frugalware.org
Miklos Vajna <vmiklos@frugalware.org> writes:
> On Wed, Jan 02, 2008 at 01:37:48PM +0100, David Kastrup <dak@gnu.org> wrote:
>> in my version of docbook2x, the --to-stdout option is broken and
>> requires the following patch:
>
> according to the INSTALL file, you need docbook2X 0.8.3. the latest
> stable 0.8.8 doesn't work here either.
Yuck. Also docbook2x seems to be available even much less
widely than other tools we use for documentation, which is
double yuck.
For now the "info" pages need to stay as a second class citizen,
it appears.
prev parent reply other threads:[~2008-01-02 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 12:37 Trouble generating info documentation David Kastrup
2008-01-02 17:05 ` Miklos Vajna
2008-01-02 18:59 ` Junio C Hamano [this message]
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=7vsl1gvysm.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=vmiklos@frugalware.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).