From: Christian Couder <chriscool@tuxfamily.org>
To: Brian Gernhardt <benji@silverinsanity.com>
Cc: Joey Hess <joey@kitenet.net>, git@vger.kernel.org
Subject: Re: [PATCH] tutorial.txt renamed
Date: Wed, 7 Jan 2009 07:07:35 +0100 [thread overview]
Message-ID: <200901070707.36263.chriscool@tuxfamily.org> (raw)
In-Reply-To: <DA6E1A83-FFBA-46BC-9BCF-ED8A2D8F12E7@silverinsanity.com>
Le mercredi 7 janvier 2009, Brian Gernhardt a écrit :
> On Jan 7, 2009, at 12:28 AM, Christian Couder wrote:
> > Le mercredi 7 janvier 2009, Joey Hess a écrit :
> >> diff --git a/README b/README
> >> index 548142c..5fa41b7 100644
> >> --- a/README
> >> +++ b/README
> >> @@ -24,7 +24,7 @@ It was originally written by Linus Torvalds with
> >> help
> >> of a group of hackers around the net. It is currently maintained by
> >> Junio
> >> C Hamano.
> >>
> >> Please read the file INSTALL for installation instructions.
> >> -See Documentation/tutorial.txt to get started, then see
> >> +See Documentation/gittutorial.txt to get started,
> >
> > "man gittutorial" and "git help tutorial" should work to display the
> > tutorial, so perhaps we should advise to use them instead of the
> > source,
> > since we are advising to use "man git-commandname" below to get help
> > on
> > each command.
>
> This is the README file for the project, so it should advise looking
> at the Documentation directory as neither the man pages or git command
> are likely installed at this point.
Well, this is debatable, because we first ask the user to read the INSTALL
file, and a tutorial for git may not be very usefull if you don't have it
installed to try out the tutorial commands.
Regards,
Christian.
next prev parent reply other threads:[~2009-01-07 6:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 4:23 [PATCH] tutorial.txt renamed Joey Hess
2009-01-07 5:28 ` Christian Couder
2009-01-07 5:36 ` Brian Gernhardt
2009-01-07 6:07 ` Christian Couder [this message]
2009-01-07 6:27 ` Junio C Hamano
2009-01-08 9:21 ` Brian Foster
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=200901070707.36263.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=benji@silverinsanity.com \
--cc=git@vger.kernel.org \
--cc=joey@kitenet.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 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).