From: Christian Couder <chriscool@tuxfamily.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, Jakub Narebski <jnareb@gmail.com>,
"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: Tue, 6 May 2008 05:11:15 +0200 [thread overview]
Message-ID: <200805060511.15293.chriscool@tuxfamily.org> (raw)
In-Reply-To: <7vy76pnzo9.fsf@gitster.siamese.dyndns.org>
Le lundi 5 mai 2008, Junio C Hamano a écrit :
> Christian Couder <chriscool@tuxfamily.org> writes:
> > Le samedi 3 mai 2008, Junio C Hamano a écrit :
> >>
> >> My preference is to move git(7) to git(1) because it is describing a
> >> command at the end-user level (distros are much better than us to come
> >> up with a way to deal with conflict resolution between us and the
> >> other git), keep file format description in section 5 (that's where
> >> they belong to).
> >
> > 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?
Some people prefer to use man pages and they like it when all the
documentation is available as man pages.
Regards,
Christian.
prev parent reply other threads:[~2008-05-06 3:07 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
2008-05-06 3:11 ` Christian Couder [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=200805060511.15293.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.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 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).