Hi, On Thu, 8 Jun 2006, Sean wrote: > On Thu, 8 Jun 2006 22:24:31 +0200 (CEST) > Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: > > > I think --user makes more sense than --home, since it does not matter > > _where_ it is stored, but _when_ it is retreived. > > --home seems more natural to me for some reason but I don't feel strongly > about it. I'd like to know how --home tells you when this key is retreived. > > In the same vein, I do not think it is user friendly to expect the user to > > remember if it was .gitconfig, .git or .gitrc. > > Sure, was just thinking that this could be used by an administrator to > modify _other_ users' configs.. but probably not worth it. The admin has no business messing around with the users' configuration. And if she absolutely wants to be a BOFH, she can fire up any editor, or copy .gitconfig to /root/.gitconfig, use git-config, and copy it back, or do what she does all the time: "su <user>". But frankly, we should not support a bad work flow. BTW it is the same reason I would rather not see /etc/gitconfig: it meddles with an existing configuration. If you want to give defaults, you can use a skeleton for $HOME, and templates for $GIT_DIR. As a user, I would be very surprised if the behaviour of git changed from one day to the other without my changing anything. Ciao, Dscho - : 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