Re: project wide: git config entry for [diff] renames=true

From: Junio C Hamano
Date: Thu Sep 25 2014 - 14:53:47 EST

Jeff King <peff@xxxxxxxx> writes:

> There is no such mechanism within git. We've resisted adding one because
> of the danger of something like:
> [diff]
> external = rm -rf /
> diff.renames is probably safe, but any config-sharing mechanism would
> have to deal with either whitelisting, or providing some mechanism for
> the puller to review changes before blindly following them.

It might be useful to add a "safe include" feature, perhaps? We
ship a small set of hardcoded default whitelist (diff.renames may be
included in there), and allow the user who do not want to be
affected to override it with

safe = !diff.renames

or even

safe = !*

at the same time allow them to add what we do not hardcode to it
using the same mechanism, e.g.

safe = merge.*


path = ../project.gitconfig

path = $HOME/.gitconfig-variant1

would only allow the variables deems safe to affect
us from the in-tree file, and use everything from my personal set in
my home directory.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at