From: "Jakub Narebski" <jnareb@gmail.com>
To: "Christian Couder" <chriscool@tuxfamily.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/3] Documentation: convert tutorials to man pages
Date: Fri, 2 May 2008 11:55:10 +0200 [thread overview]
Message-ID: <8fe92b430805020255r1a06e169te583c371bde83ade@mail.gmail.com> (raw)
In-Reply-To: <20080502053051.c8066c4e.chriscool@tuxfamily.org>
On 5/2/08, Christian Couder <chriscool@tuxfamily.org> wrote:
> This patch renames the following documents and at the same time converts
> them to the man page format:
>
> cvs-migration.txt -> gitcvs-migration.txt
> everyday.txt -> giteveryday.txt
> tutorial.txt -> gittutorial.txt
> tutorial-2.txt -> gittutorial-2.txt
I like the rest of the series, but this I have serious doubts about. I think
that manpage format is just not suitable for guides and tutorials (larger
works), especially that we have HTML and beginnings of info versions.
Beside, the filenames looks stupid... githooks would go in a pinch, but
other names...
--
Jakub Narebski
next prev parent reply other threads:[~2008-05-02 9:56 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 [this message]
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
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=8fe92b430805020255r1a06e169te583c371bde83ade@mail.gmail.com \
--to=jnareb@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.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).