From: Paul Eggert <eggert@cs.ucla.edu>
To: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Why does make run git?
Date: Tue, 1 Aug 2017 08:10:59 -0700 [thread overview]
Message-ID: <056f3714-9c2d-3983-ab48-f677da0718d1@cs.ucla.edu> (raw)
In-Reply-To: <E1dcLqh-0006x8-7C@fencepost.gnu.org>
Richard Stallman wrote:
> I was surprised to see this output from `make'. What does this do?
> It seems fundamentally unmodular for building Emacs from sources
> to concern itself in any way with how you got those sources.
Make configures Git only if you got the sources via Git and have not configured
Emacs. If you got the sources via some other means, or have already configured
Emacs, Make doesn't configure Git. So I don't see a violation of modularity
here; it's merely a convenience that Make supplies a default configuration if
you haven't already configured things.
If you prefer to not configure Git even though you got the sources via Git, you
can run 'make ALL_IF_GIT=' or './configure; make' after grabbing the sources.
However, the default Git configuration is typically more convenient.
> Running make on the Emacs checkout seems like an inadequate place to
> do this. There is no assurance that you will run make in that
> checkout before committing anything.
That's true. However, these are only guidelines, and it's not a huge tragedy if
the guidelines are occasionally violated.
> Perhaps there should be a function in Emacs that does this, and some
> VC commands could call it.
That would be nice. However, some developers don't use Emacs VC to check in (I
typically use vc-dwim instead), and so it's good to have Git check things as well.
next prev parent reply other threads:[~2017-08-01 15:10 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=056f3714-9c2d-3983-ab48-f677da0718d1@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=rms@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.