From: Tino Calancha <tino.calancha@gmail.com>
To: Richard Stallman <rms@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: Why does make run git?
Date: Tue, 1 Aug 2017 23:49:08 +0900 (JST) [thread overview]
Message-ID: <alpine.DEB.2.20.1708012340501.27552@calancha-pc> (raw)
In-Reply-To: <E1dcYBw-0004TB-Dz@fencepost.gnu.org>
On Tue, 1 Aug 2017, Richard Stallman wrote:
> [[[ To any NSA and FBI agents reading my email: please consider ]]]
> [[[ whether defending the US Constitution against all enemies, ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
> > > git config transfer.fsckObjects 'true'
>
> > This makes Git abort if it sees a bad object being pulled or pushed.
>
> Isn't that a personal preference? It seems wrong for Emacs to set it
> arbitrarily.
It's recommended for security. It was discussed before being
added:
https://lists.gnu.org/archive/html/emacs-devel/2016-01/msg01802.html
> > > git config diff.elisp.xfuncname '^\(def[^[:space:]]+[[:space:]]+([^()[:space:]]+)'
> > > git config diff.m4.xfuncname '^((m4_)?define|A._DEFUN(_ONCE)?)\([^),]*'
> > > git config diff.make.xfuncname '^([$.[:alnum:]_].*:|[[:alnum:]_]+[[:space:]]*([*:+]?[:?]?|!?)=|define .*)'
> > > git config diff.shell.xfuncname '^([[:space:]]*[[:alpha:]_][[:alnum:]_]*[[:space:]]*\(\)|[[:alpha:]_][[:alnum:]_]*=)'
> > > git config diff.texinfo.xfuncname '^@node[[:space:]]+([^,[:space:]][^,]+)'
>
> > These tailor the Git's notion of a "function" for the various
> > languages. It's handy in several commands that need to know where a
> > function begins and ends.
>
> Do you mean, several Git commands, or several Emacs commands?
> I would guess it is the former.
>
> 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.
>
> Perhaps there should be a function in Emacs that does this, and some
> VC commands could call it.
I think is for convenience. It is set there once and for all. There
are plenty of Git interfaces for Emacs out of there: whatever an user
decide to use, s?he already has set up those hooks; then her/him
potential contributions will be easier accepted.
next prev parent reply other threads:[~2017-08-01 14:49 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 [this message]
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
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=alpine.DEB.2.20.1708012340501.27552@calancha-pc \
--to=tino.calancha@gmail.com \
--cc=eliz@gnu.org \
--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.