From: "Mike Ralphson" <mike.ralphson@gmail.com>
To: SLONIK.AZ@gmail.com, "Git Mailing List" <git@vger.kernel.org>
Cc: "Junio C Hamano" <gitster@pobox.com>, "Jeff King" <peff@peff.net>,
"Miklos Vajna" <vmiklos@frugalware.org>
Subject: Re: request for pre-generated git.info pages
Date: Thu, 30 Oct 2008 12:01:53 +0000 [thread overview]
Message-ID: <e2b179460810300501s5569b03ej56616a8ab1c8c28e@mail.gmail.com> (raw)
In-Reply-To: <e2b179460810300206g79e06c63m2060092fa654b18b@mail.gmail.com>
2008/10/30 Mike Ralphson <mike.ralphson@gmail.com>:
> Unfortunately I don't have a working asciidoc etc toolchain either
> (though I will take a look at getting it working on my central git box
> which is Linux based). As I'm not an emacs or Info user I probably
> wouldn't know if they were building correctly anyway.
The only machine at my disposal with a working Python installation
(and I'm afraid I don't feel inclined to install it anywhere else,
Python on AIX is painful, and obviously if I was a Python nut, I'd be
running mercurial anyway, right?) is my desktop cygwin installation.
At least there obtaining asciidoc was no problem, but I think I'm
stuck in some docbook2x dependency hell with lots of twisty turny
prerequisities, all alike.
Now deep in a dark cave with a sign saying "Can't locate
XML/Handler/SGMLSpl.pm in @INC", which is where my adventure ends.
Score 0/100.
So a volunteer would still be appreciated.
Mike
next prev parent reply other threads:[~2008-10-30 12:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 22:00 request for pre-generated git.info pages Leo Razoumov
2008-10-30 9:06 ` Mike Ralphson
2008-10-30 9:33 ` Miklos Vajna
2008-10-30 12:01 ` Mike Ralphson [this message]
2008-10-30 23:06 ` Kalle Olavi Niemitalo
2008-10-31 0:19 ` Kalle Olavi Niemitalo
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=e2b179460810300501s5569b03ej56616a8ab1c8c28e@mail.gmail.com \
--to=mike.ralphson@gmail.com \
--cc=SLONIK.AZ@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--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).