On Tue, 30 Jan 2007 12:13:26 -0800, Carl Worth wrote: > I'm finding that the instructions I'm having to write are much more > complicated than I would like them to be. And some of this is due to > incompatibility between git 1.5 and previous versions. When I first brought up this thread we had lots of good discussion about detached head that led to improved (or eliminated) warning messages, and some good motivation for HEAD reflog. Meanwhile, there's still a piece of the original problem that was not addressed: > git checkout -b build origin/proposed-fix > > I really like most of what separate-remotes does. But I don't like > that branch names no longer resolve the same way they used to. Could > we fix git to resolve "branch" as "remotes/*/branch" if unique? That > would allow the old instructions and old habits to continue to work, > (making the change to separate-remotes much more compatible). Is there any feedback on the above? I just ran into this problem again tonight, giving out instructions of "git checkout -b build proposed-fix" and then bracing myself to have the user complain about an error of: git checkout: updating paths is incompatible with switching branches/forcing Did you intend to checkout 'proposed-fix' which can not be resolved as commit? To which I'd have to respond, "Oh, you're using a newer git. In your case use 'git checkout -b build origin/proposed-fix'". So, could we fix this so that a remote branch name will resolve without the "origin/" prefix if it is not ambiguous? I can imagine the resolution rules are already fairly complicated, (I don't even know what they all are already). But when there is no ambiguity, and when the behavior would be backwards compatible to git before separate-remotes, is there any reason this would be a bad idea? Thanks, -Carl
Attachment:
pgpR4R8xmHR5z.pgp
Description: PGP signature