On Fri, May 25, 2012 at 07:54:06PM +0200, Matthieu Moy wrote: > Having a $GIT_WORKTREE/.gitconfig file would be very nice, but raises a > lot of security issues, so it's a much larger project (define which > configuration values are allowed there, possibly take them into account > at clone time, i.e. before checking out the files, and so on). Most > likely out of the scope of my students' project ;-). Yes, I have proposed it in multiple forms, and the discussion always ends in "gross, it's too complex". If you really want to do it, the recommended way at this point is: # review for any issues (1) less .gitconfig # assuming it's OK, copy into place (2) cp .gitconfig .git/config-from-upstream # include it git config include.path config-from-upstream And then repeat steps (1) and (2) whenever you want to update from upstream. That fixes not only the security issues, but also means that you won't accidentally drop back to some antique bogus config when you "git checkout $some_old_version". -Peff -- 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