From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: Jeff King <peff@peff.net>, Jakub Narebski <jnareb@gmail.com>,
"J. Bruce Fields" <bfields@fieldses.org>,
git@vger.kernel.org
Subject: Re: [PATCH 3/3] Documentation: convert tutorials to man pages
Date: Sat, 03 May 2008 10:44:57 -0700 [thread overview]
Message-ID: <7vfxszuvs6.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 200805030604.32123.chriscool@tuxfamily.org
Christian Couder <chriscool@tuxfamily.org> writes:
> About man page sections, Perl is consistent because every thing is in
> section 1.
I do not think it is a good example to follow, though.
> Now for git we already have git commands in section 1 and some
> other documentation (gitattributes, gitignore, gitmodules) in section 5
> and "git" in section 7. Do we want to keep "git" alone in section 7 and put
> tutorials in section 1 ? Or put everything in section 1 ?
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).
next prev parent reply other threads:[~2008-05-03 17:46 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 [this message]
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
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=7vfxszuvs6.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=bfields@fieldses.org \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=peff@peff.net \
/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.