From: Thiago Farina <tfransosi@gmail.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Alex Riesen <raa.lkml@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] Add more instructions about how to install git.
Date: Tue, 8 Sep 2009 11:24:37 -0300 [thread overview]
Message-ID: <a4c8a6d00909080724q1c792f6bs641ea9d000d08b5a@mail.gmail.com> (raw)
In-Reply-To: <vpqhbvekldk.fsf@bauges.imag.fr>
On Tue, Sep 8, 2009 at 3:20 AM, Matthieu
Moy<Matthieu.Moy@grenoble-inp.fr> wrote:
> Your commit message doesn't say what's wrong with
>
> | Alternatively you can use autoconf generated ./configure script to
> | set up install paths (via config.mak.autogen), so you can write
> | instead
> |
> | $ make configure ;# as yourself
> | $ ./configure --prefix=/usr ;# as yourself
> | $ make all doc ;# as yourself
> | # make install install-doc install-html;# as root
>
> which is already in INSTALL a few lines after what your patch adds.
I tried to being more explicit about what the new users has to do. The
first instruction that the text says is: "Normaly you can just do
"make"".
But the new user, cloning git won't have a configure file, so he can't
just do "make".
And then, the text says: "so you can write instead". This brings me to
one alternative (not what I really should do), when in fact it should
be (I guess) the first instructions that new users need to follow.
next prev parent reply other threads:[~2009-09-08 14:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 5:11 [PATCH] Add more instructions about how to install git Thiago Farina
2009-09-08 5:44 ` Alex Riesen
2009-09-08 6:20 ` Matthieu Moy
2009-09-08 7:56 ` Michael J Gruber
2009-09-08 14:24 ` Thiago Farina [this message]
2009-09-08 14:37 ` Erik Faye-Lund
2009-09-08 14:38 ` Johannes Sixt
2009-09-08 14:52 ` Thiago Farina
2009-09-08 14:56 ` Mikael Magnusson
2009-09-08 15:19 ` Brian Gernhardt
2009-09-08 19:41 ` Matthieu Moy
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=a4c8a6d00909080724q1c792f6bs641ea9d000d08b5a@mail.gmail.com \
--to=tfransosi@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=raa.lkml@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).