From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, rms@gnu.org, tino.calancha@gmail.com
Subject: Re: Why does make run git?
Date: Wed, 2 Aug 2017 11:42:43 -0700 [thread overview]
Message-ID: <02f6233d-b0ef-5a8f-9089-f3fc3496df02@cs.ucla.edu> (raw)
In-Reply-To: <83a83hzuqv.fsf@gnu.org>
On 08/02/2017 11:31 AM, Eli Zaretskii wrote:
>> To help improve the situation I propose the attached patch, which
>> reverts the default ./autogen.sh behavior to be './autogen.sh all', the
>> way it used to be (briefly). Developers who want autogen.sh to leave
>> their Git settings alone can continue to use './autogen.sh autoconf'.
> AFAIU, doing that will silently force the installation of the
> Git-related stuff when I run just "make", and Make decides it needs to
> invoke autogen.sh, because the fact that I originally used the
> non-default argument isn't recorded anywhere, and thus cannot be
> replayed. Right?
No, if you run Make from a freshly-checked-out directory, Make calls
"./autogen.sh all", which sets up Git. The proposed patch doesn't affect
this.
And if you run "./autogen.sh autoconf" and then run Make, Make won't set
up Git. The proposed patch doesn't affect this either.
The only thing that changes is what happens if you run plain "./autogen.sh".
next prev parent reply other threads:[~2017-08-02 18:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 1:19 Why does make run git? Richard Stallman
2017-08-01 3:07 ` Eli Zaretskii
2017-08-01 14:30 ` Richard Stallman
2017-08-01 14:49 ` Tino Calancha
2017-08-02 17:26 ` Richard Stallman
2017-08-02 17:43 ` Radon Rosborough
2017-08-03 19:43 ` Richard Stallman
2017-08-03 20:02 ` Radon Rosborough
2017-08-02 17:56 ` Paul Eggert
2017-08-02 18:31 ` Eli Zaretskii
2017-08-02 18:42 ` Paul Eggert [this message]
2017-08-02 19:10 ` Eli Zaretskii
2017-08-02 20:04 ` Paul Eggert
2017-08-12 16:11 ` Paul Eggert
2017-08-15 14:18 ` Ted Zlatanov
2017-08-15 15:52 ` Paul Eggert
2017-08-15 16:58 ` Ted Zlatanov
2017-08-15 17:08 ` Eli Zaretskii
2017-08-15 20:39 ` Paul Eggert
2017-08-16 12:30 ` Andy Moreton
2017-08-16 12:38 ` Noam Postavsky
2017-08-16 12:49 ` Andreas Schwab
2017-08-16 14:09 ` Ted Zlatanov
2017-08-01 3:14 ` Tino Calancha
2017-08-02 17:25 ` Richard Stallman
2017-08-01 15:10 ` Paul Eggert
2017-08-01 15:15 ` Kaushal Modi
2017-08-01 16:01 ` Radon Rosborough
2017-08-02 17:30 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=02f6233d-b0ef-5a8f-9089-f3fc3496df02@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=tino.calancha@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).