On Thu, 17 Apr 2008, Jeremy Maitin-Shepard wrote: > > There is a huge difference: if you allow in-tree .gitconfig by default, > then git clone <some-repository> becomes an unsafe operation. I have to agree. The git config file is rather powerful, with things like aliases etc that can be used to run external programs (and with the external diff functionality that includes it for very basic and default operations), and ways of subtly (and not so subtly) rewriting repository information etc etc. So if we do end up doing a "tracked config file", I'd personally very much prefer it be limited in some way. For example, we obviously track the .gitignore and .gitattributes files, but they are much more limited in their effects. Maybe we could have a "limited config file" that allows for *some* config options to be set? Linus -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
