From: Christian Couder <chriscool@tuxfamily.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: "しらいしななこ " <nanako3@bluebottle.com>,
"Pieter de Bie" <pdebie@ai.rug.nl>,
"Jakub Narebski" <jnareb@gmail.com>,
"Manoj Srivastava" <srivasta@ieee.org>,
"Thomas Adam" <thomas.adam22@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH v3] Documentation: convert tutorials to man pages
Date: Sun, 25 May 2008 06:57:57 +0200 [thread overview]
Message-ID: <200805250657.57568.chriscool@tuxfamily.org> (raw)
In-Reply-To: <7vlk1zjh4x.fsf@gitster.siamese.dyndns.org>
Le dimanche 25 mai 2008, Junio C Hamano a écrit :
> しらいしななこ <nanako3@bluebottle.com> writes:
> > Christian Couder <chriscool@tuxfamily.org> writes:
> >
> > However, I think this is much improved, compared to the one around the
> > beginning of the month. Especially that documents like the user manual
> > that do not fit well in "manual page" format are excluded.
> >
> > But if I read intro(1) and intro(7) correctly, nothing other than the
> > user commands should go to section 1. Here is my attempt, as a
> > replacement patch, to clean it up.
> >
> > What do you think?
>
> Christian, I think the amended patch makes more sense (I haven't compared
> the two very carefully, though).
Nanako's amended patch looks good to me too.
Tested-by: Christian Couder <chriscool@tuxfamily.org>
So please apply.
Thanks to Nanako and you,
Christian.
next prev parent reply other threads:[~2008-05-25 4:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-24 18:56 [PATCH v3] Documentation: convert tutorials to man pages Christian Couder
2008-05-25 1:12 ` しらいしななこ
2008-05-25 1:40 ` Junio C Hamano
2008-05-25 4:57 ` Christian Couder [this message]
2008-05-25 8:02 ` Junio C Hamano
2008-05-25 1:29 ` Junio C Hamano
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=200805250657.57568.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=nanako3@bluebottle.com \
--cc=pdebie@ai.rug.nl \
--cc=srivasta@ieee.org \
--cc=thomas.adam22@gmail.com \
/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).