From: Radon Rosborough <radon.neon@gmail.com>
To: rms@gnu.org
Cc: eliz@gnu.org, emacs-devel@gnu.org, tino.calancha@gmail.com
Subject: Re: Why does make run git?
Date: Thu, 3 Aug 2017 13:02:04 -0700 [thread overview]
Message-ID: <CADB4rJEmsuZZy3fj+ZQudh=Fc9Z7EPHbiNNGXdzBb9enFwebBQ@mail.gmail.com> (raw)
In-Reply-To: <E1ddM1V-0003v2-J2@fencepost.gnu.org>
> We could make it a documented Emacs facility,
> which could be used by any repository, and all front-ends ought
> to call it.
I don't object, but this sounds a little bit like overkill to me. This
would be a significant amount of added complexity (e.g. notifying all
known authors of version-control packages [maybe not that many?] and
hoping they incorporate supporting changes; dealing with safety [is
safe-local-variable-values enough?]; working out the appropriate scope
[is this just for Git? can you also run arbitrary shell commands?];
designing an interface that will cover all common use cases; making
sure that this doesn't impact performance; deciding whether to
override existing configuration and hooks; etc.), and it still doesn't
really fix the problem since plenty of people will just use Git
directly.
I'd vote for leaving the situation as-is, since there's no general way
to prevent people from using Git without first configuring it. The
"right" solution is to not rely on the local Git configuration for
anything mission-critical.
OTOH, since this is a relatively common problem, maybe somebody has
already invented a general-purpose solution. In that case perhaps
Emacs should support that standard. I don't think Emacs should create
its own standard in this case.
next prev parent reply other threads:[~2017-08-03 20:02 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 [this message]
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
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='CADB4rJEmsuZZy3fj+ZQudh=Fc9Z7EPHbiNNGXdzBb9enFwebBQ@mail.gmail.com' \
--to=radon.neon@gmail.com \
--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 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.