From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: martin rudalics <rudalics@gmx.at>,
emacs-devel <emacs-devel@gnu.org>,
Andreas Schwab <schwab@suse.de>,
Yuri Khan <yuri.v.khan@gmail.com>
Subject: Re: git pre-commit hook for merges (WAS: master has switched from Automake to GNU Make)
Date: Thu, 13 Apr 2017 16:04:21 -0400 [thread overview]
Message-ID: <CAM-tV-9b0Gt4saFeSnzVRjNcH=EQgpSYzDqHxfZAJ=FFYzHXDw@mail.gmail.com> (raw)
In-Reply-To: <513c116f-2af5-19de-697d-583961b44e2e@cs.ucla.edu>
On Thu, Apr 13, 2017 at 2:11 AM, Paul Eggert <eggert@cs.ucla.edu> wrote:
> It's better if './configure' does not mess with Git settings, yes.
> './configure' has always been intended to operate independently of whether
> the source is under version control, and to operate after all the autotools
> have been run to set things up.
It seems preferable to me if the hooks could be managed by
./configure, and furthermore be updated by 'make' (as we have at least
one case of someone running with outdated hooks). Git's hooks are
unrelated to autotools regardless.
next prev parent reply other threads:[~2017-04-13 20:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 16:25 git pre-commit hook for merges (WAS: master has switched from Automake to GNU Make) Noam Postavsky
2017-04-12 9:30 ` martin rudalics
2017-04-12 18:26 ` Paul Eggert
2017-04-13 0:13 ` Noam Postavsky
2017-04-13 1:49 ` Paul Eggert
2017-04-13 2:05 ` Noam Postavsky
2017-04-13 6:11 ` Paul Eggert
2017-04-13 20:04 ` Noam Postavsky [this message]
2017-04-29 18:00 ` Noam Postavsky
2017-04-29 18:44 ` Paul Eggert
2017-04-29 19:15 ` Eli Zaretskii
2017-04-29 19:54 ` Noam Postavsky
2017-04-29 20:04 ` Eli Zaretskii
2017-04-29 23:25 ` Noam Postavsky
2017-04-30 2:34 ` Eli Zaretskii
2017-04-30 19:35 ` Noam Postavsky
2017-04-30 19:40 ` Eli Zaretskii
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='CAM-tV-9b0Gt4saFeSnzVRjNcH=EQgpSYzDqHxfZAJ=FFYzHXDw@mail.gmail.com' \
--to=npostavs@users.sourceforge.net \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
--cc=schwab@suse.de \
--cc=yuri.v.khan@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 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.