On Feb 4, 2008 9:48 AM, Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: > Hi, > > > Should something like core.origin still be an issue (which I doubt, for > the same reason you do not change the _name_ of the environment variable > $HOME), we can still continue discussing that. > > Hth, > Dscho > > BIG difference here: $HOME = <name> of home directory, <name> is arbitrary. Files there are found as $HOME/<foo> or <name>/foo, they are the same, and I am free to set HOME=<arbitrary name>. Currently $ORIGIN=origin, i.e., the default is *named* origin, not the default name is given by $ORIGIN. Why does this matter? git stores the remote's branches under refs/remotes/<name>/*. If name=$ORIGIN, I am happy, but the problem is $ORIGIN=origin, and you argue (strongly) that it MUST be origin. Thus, branches from server "frotz" *might* be in refs/remotes/frotz/*, or they *might* be in refs/remotes/origin/*, and that is the root of the problem. By the same argument, you have hardcoded in your shell that $HOME=/home, right? Mark - 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