On Fri, 13 Apr 2007 09:46:45 +1200, Martin Langhoff wrote: > Hi Carl! Yes - this stuff should be simple, and _really hard to fsck up_. I definitely agree. I think the use case of "tracking some branch other than the default" is a really important one to make easy. Precisely because there are a lot of users who will initially use git for nothing other than this tracking, (not initially making commits, or pushing, etc.). So we would do well if this initial exposure were really easy. And right now it's a bit too hard in my opinion, (in terms of commands, concepts, and syntax the user has to use). Is this correct sequence for the operation in 1.5.1 ? git clone <repo> cd <project> git branch --track <branch> origin/<branch> git checkout branch git pull # as needed I'd love to get that down to: git clone <something with <repo> and <branch>> cd <project> git pull # as needed and then adding a subsequent branch to track would be: git track <something with <repo> and <branch>> git checkout <branch> git pull # as needed > Oops - looks like we are talking about different things. What you write > above can be done with "git-branch --track" on 1.5.1 so it's already in > existence. The mechanics are there, yes. All that's missing is the common <something> syntax which, as shown above, can be shared for both cloning originally and later adding a branch to track. And <repo>#<branch> seems as good a <something> as anything else I could imagine. > With my proposed git-track as a wrapper around git-clone _and_ > git-branch --track, you only need to say > > To start working on foo, do > > git track <repo>#branch Yeah, that's the idea. I had just planned on publishing the <repo>#branch part and the user would learn whether to pass that to "git clone" or "git track" as appropriate. Making one command do either one seems a little too DWIM and error-prone to me. But whatever works, (and more importantly, whatever you can implement and get accepted). -Carl
Attachment:
pgpUFEbrfw3RS.pgp
Description: PGP signature