From: Junio C Hamano <gitster@pobox.com>
To: Miles Bader <miles@gnu.org>
Cc: gyles19@visi.com,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: Re: Chicken/egg problem building from a 'git clone'
Date: Fri, 06 Feb 2009 02:28:48 -0800 [thread overview]
Message-ID: <7vd4dv7tb3.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <buoab8z52te.fsf@dhlpc061.dev.necel.com> (Miles Bader's message of "Fri, 06 Feb 2009 18:31:41 +0900")
Miles Bader <miles@gnu.org> writes:
> Junio C Hamano <gitster@pobox.com> writes:
>>
>> Please do not encourge use of configure/autoconf *in this project*.
>
> Er ... I was not doing so. I was saying that if one is going to use
> autoconf with git, one should use a non-ancient version.
That is nice but the statement is only half-truth, and should be followed
by ", but why bother? You do not even need to use configure to build
git, and insn is all here...".
Omitting that latter half and instead having him spend time to update
autoconf, which is not even needed, sounds like strongly encouraging its
use to me.
> I don't think merely discussing autoconf+git without pejorative asides
> is "encouraging use".
"You should use recent enough autoconf *if* you want to use configure, but
why bother? You do not even need to use configure to build git, and here
is how..." does not say anything pejorative about autoconf, either, and it
is certainly not encouraging its use.
On the other hand, omitting "but why bother?" part is, and the reason is
not because it does not badmouth autoconf, but because use of autoconf is
non-essential in this project.
next prev parent reply other threads:[~2009-02-06 10:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 4:09 Chicken/egg problem building from a 'git clone' Joi Ellis
2009-02-06 4:32 ` Johannes Schindelin
2009-02-06 4:45 ` Joi Ellis
2009-02-06 5:12 ` Miles Bader
2009-02-06 5:36 ` Junio C Hamano
2009-02-06 5:49 ` Miles Bader
2009-02-06 8:12 ` Junio C Hamano
2009-02-06 9:31 ` Miles Bader
2009-02-06 10:28 ` Junio C Hamano [this message]
2009-02-06 10:35 ` Miles Bader
2009-02-06 19:25 ` Jeff King
2009-02-06 22:12 ` Junio C Hamano
2009-03-01 15:56 ` Joi Ellis
2009-03-01 16:34 ` Björn Steinbrink
2009-03-05 9:06 ` Andreas Ericsson
2009-03-05 11:37 ` John Tapsell
2009-03-05 12:06 ` Jeff King
2009-03-05 12:38 ` Matthieu Moy
2009-03-05 12:45 ` Jeff King
2009-03-06 10:39 ` Jakub Narebski
2009-03-06 10:51 ` Matthieu Moy
2009-03-06 11:04 ` Johannes Schindelin
2009-03-06 11:27 ` John Tapsell
2009-03-06 12:02 ` asciidoc, was " Johannes Schindelin
2009-03-06 12:28 ` John Tapsell
2009-03-06 13:15 ` Jakub Narebski
2009-03-06 13:39 ` John Tapsell
2009-02-06 5:14 ` Björn Steinbrink
2009-02-06 11:34 ` Johannes Schindelin
2009-02-06 4:44 ` Björn Steinbrink
2009-02-06 19:06 ` Daniel Barkalow
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=7vd4dv7tb3.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gyles19@visi.com \
--cc=miles@gnu.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).