Re: Recommend these .gitconfig settings for git integrity.

[Paul Eggert]

On 02/03/2016 07:47 AM, Eli Zaretskii wrote:
> No objections here, but I wonder: how is that different from just
> telling people who track the development to run the corresponding
> "git config" command?  Both require a deliberate action, and neither
> of the commands is significantly more complex than the other one.
I'm afraid it's more complicated than that. './autogen.sh all' currently 
configures three Git variables with values like 
'^\(def[^[:space:]]+[[:space:]]+([^()[:space:]]+)', avoids touching the 
configuration if it's already correct for other reasons, and on 
GNU/Linux hosts makes backups of all its configuration-file changes. I'd 
hate to cut and paste all that stuff out of a text file.