On Wed, 15 Nov 2006, Andy Parkins wrote: > On Wednesday 2006 November 15 04:32, Nicolas Pitre wrote: > > > OK..... let's pretend this is my follow-up to your "If I were redoing > > Personally, I agree with almost everything in this email. Except the > implementation of point 3. > > > 3) remote branch handling should become more straight forward. > > I was completely confused by this origin/master/clone stuff when I started > with git. In hindsight, now I understand git a bit more, this is what I > would have liked: > > * Don't use the name "origin" twice. In fact, don't use it at all. In a > distributed system there is no such thing as a true origin. I agree, sort of. Not because"origin" is ambigous as a name. But rather because there is a magic translation from "master" to "origin", and I think this is wrong to do that. As mentioned elsewhere (and let's start using "get" instead of "pull" as suggested by Johannes), a "get" should probably always create a branch group even if it contains only one branch. This way the remote branch called "master" will still be called "master" locally, under the branch group used to represent the remote repository. And if a local name is not provided then let's just call it "default". This way, amongst the remote references, there would be a "default/master" that would be used when nothing else is provided by the user. So... git get repo.com/time_machine.git would create a local branch named "remotes/default/master" if the remote repo has only a master branch. Then, a simple: git merge could be the same as git merge default which would be equivalent to git merge default/master Afterwards, because the "default" remote already exists, then: git get would be the same as git get default to get changes for all branches in the "default" remote branches, of which "master" might be the only one in the simple case. But again I think it is important that the URL to use must be a per branch attribute i.e. attached to "default/master" and not just "default". This way someone could add all branches of interest into the "default" group even if they're from different repositories, and a simple get without any argument would get them all. Nicolas - 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