threads / discuss / 17050

Plans to put together an Info manual?

Subject: Plans to put together an Info manual?

## tl;dr

2 messages between Jan 8, 2009 and Jan 8, 2009.

replies: 1people: 2as markdown or json

Tim Visher· Jan 8, 2009, 15:47 UTC · lore

I did a _teensy_ bit of googling and nosing around on the home page, so forgive me if this has been brought up before or if it in fact already exists.

I wast just wondering A) If there is an info manual for Git, B) If there isn't, is one planned?

I'm personally a big fan of Info manuals over traditional man pages but I have no experience with creating them or anything like that. However, this might be another nice place for people who aren't at all familiar with C (read: me) to jump in and help out with development.

-- 
In Christ,

Timmy V.

http://burningones.com/
http://five.sentenc.es/ - Spend less time on e-mail
Teemu Likonen· Jan 8, 2009, 17:09 UTC · re: Tim Visher · lore

Re: Plans to put together an Info manual?

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.

← back to recent threads