Quoting Moe <moe@xxxxxxxxxxxxxx> > In practice our developers will su or ssh to this user to get working > and generally they need only a very small set of divertions from the > common configuration - such as their personal git identity and their > preferred editor settings. Do "preferred editor settings" mean $HOME/.vim that was one of Junio's examples? How do you handle it? It sounds like you are only interested in user.name and user.email, and you don't need to override $HOME/.gitconfig as a whole. Because you already have a section in $HOME/.bashrc that does different things based on the user's SSH key, you may want to set variables GIT_AUTHOR_NAME and GIT_AUTHOR_EMAIL in there without doing anything else if that is the case. > One may argue that a bunch of host-specific symlinks could achieve a > similar effect - and that would be correct - but having literally > everything under version control yields certain advantages that we > wouldn't want to miss. Sorry, but I don't understand. What do symlinks have to do with keeping everything under version control? git can track symbolic links just fine, if that is what is troubling you. -- Nanako Shiraishi http://ivory.ap.teacup.com/nanako3/ -- 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