[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why does make run git?

From: Eli Zaretskii
Subject: Re: Why does make run git?
Date: Tue, 01 Aug 2017 06:07:04 +0300

> From: Richard Stallman <address@hidden>
> Date: Mon, 31 Jul 2017 21:19:51 -0400
> I was surprised to see this output from `make'.  What does this do?

Configure Git commands for Emacs, mostly.

> It seems fundamentally unmodular for building Emacs from sources
> to concern itself in any way with how you got those sources.

It is indeed somewhat controversial.

> git config transfer.fsckObjects 'true'

This makes Git abort if it sees a bad object being pulled or pushed.

> 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 
> 'address@hidden: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.

> Installing git hooks...
> ‘build-aux/git-hooks/commit-msg’ -> ‘.git/hooks/commit-msg’
> ‘build-aux/git-hooks/pre-commit’ -> ‘.git/hooks/pre-commit’
> ‘.git/hooks/applypatch-msg.sample’ -> ‘.git/hooks/applypatch-msg’
> ‘.git/hooks/pre-applypatch.sample’ -> ‘.git/hooks/pre-applypatch’

These hooks check the format of the commits and verify it is
according to our standards.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]