From: Teemu Likonen <tlikonen@iki.fi>
To: "Tim Visher" <tim.visher@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Plans to put together an Info manual?
Date: Thu, 08 Jan 2009 19:09:35 +0200 [thread overview]
Message-ID: <87vdspk9m8.fsf@iki.fi> (raw)
In-Reply-To: <c115fd3c0901080747p4dd1233fla2f877f39ffa9806@mail.gmail.com> (Tim Visher's message of "Thu\, 8 Jan 2009 10\:47\:20 -0500")
Tim Visher (2009-01-08 10:47 -0500) wrote:
> I wast just wondering A) If there is an info manual for Git, B) If
> there isn't, is one planned?
There is already something that _can_ be called "info manual for Git".
It's basically info version of Git User's Manual:
http://www.kernel.org/pub/software/scm/git/docs/user-manual.html
Regular man pages are also available in info format.
The info manuals are not written in native info format, though. They are
generated from the asciidoc markup files, through xml format. There are
some problems with typesetting as some characters simply disappear in
the "asciidoc -> xml -> texi -> info" conversion. Two dashes (--) turn
into one (-), for example. But if you are not too demanding the info
manuals are quite usable. You can compile them with "make info" command.
prev parent reply other threads:[~2009-01-08 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 15:47 Plans to put together an Info manual? Tim Visher
2009-01-08 17:09 ` Teemu Likonen [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=87vdspk9m8.fsf@iki.fi \
--to=tlikonen@iki.fi \
--cc=git@vger.kernel.org \
--cc=tim.visher@gmail.com \
/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).