From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Christian Couder <chriscool@tuxfamily.org>,
Jeff King <peff@peff.net>,
"J. Bruce Fields" <bfields@fieldses.org>,
"Manoj Srivastava" <srivasta@ieee.org>,
"Ping Yin" <pkufranky@gmail.com>,
git@vger.kernel.org
Subject: Re: Documentation status
Date: Mon, 5 May 2008 09:34:38 +0200 [thread overview]
Message-ID: <200805050934.40851.jnareb@gmail.com> (raw)
In-Reply-To: <7vy76pnzo9.fsf@gitster.siamese.dyndns.org>
Junio C Hamano wrote:
> Christian Couder <chriscool@tuxfamily.org> writes:
[...]
>> Ok, I will do that.
>> Then what about tutorials (that I put in section 7) ?
>
> Please step back a bit. What's the reason why you need to make
> everything into manpages?
I think the main idea was to make into manpages all documentation which
is referenced from manpages, perhaps with the exception of
documentation listed in git(7)/git(1).
This way one use man viewer such as 'pinfo', and follow references to
other manpages...
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2008-05-05 7:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 3:30 [PATCH 3/3] Documentation: convert tutorials to man pages Christian Couder
2008-05-02 9:55 ` Jakub Narebski
2008-05-02 12:49 ` Jeff King
2008-05-02 14:31 ` J. Bruce Fields
2008-05-03 4:04 ` Christian Couder
2008-05-03 17:44 ` Junio C Hamano
2008-05-05 3:48 ` Documentation status (was Re: [PATCH 3/3] Documentation: convert tutorials to man pages) Christian Couder
2008-05-05 4:27 ` Documentation status Junio C Hamano
2008-05-05 7:34 ` Jakub Narebski [this message]
2008-05-06 3:11 ` Christian Couder
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=200805050934.40851.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=bfields@fieldses.org \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=pkufranky@gmail.com \
--cc=srivasta@ieee.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.