On Tue, Mar 10, 2009 at 09:37:21PM -0700, Junio C Hamano wrote: > In any case, I find these "branch --retrack" proposals too confusing and > probably overengineered. I agree. I was hoping to find something that _wasn't_ confusing, but I don't think we've succeeded. > I need to ask a more fundamental question. Is it really useful for people > to be able to re-track arbitrary remote/branch with an existing branch? I do it occasionally, but I have never had a problem with editing .git/config. My use case is usually something like: 1. make an experimental commit on some long-running branch like 'next' or 'master' 2. realize it's going to take several commits and would work better as a topic branch 3. git checkout -b topic in which case I have no tracking setup. But if I had realized it was going to be a topic in the first place and done "git checkout -b topic origin/master" then I would. But again, I don't have a problem with editing .git/config. I was trying in this thread to respond to user request. -Peff -- 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