Web lists-archives.com

Re: bug during checkout of remote branch and uncommited changes ?

Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx> writes:

> 	$ git reset --hard
> 	patching file afile.c

Is that a message from something?  It does not sound like something
"git reset --hard" would say.

> 	$ git co <abranch>
> 	fatal: Not tracking: ambiguous information for ref refs/remotes/<aremote>/<abranch>
> What can be ambiguous here?

I think the message "Not tracking" is given when there is a remote
other than <aremote> that also has <abranch>.  Between the time you
got the message and the time you tried to checkout <abranch>, did
anything happen to cause the second attempt succeed?

> Strangely, trying a second time, succeed:
> 	$ git co <abranch>
> 	Previous HEAD position was ...
> 	Switched to branch '<abranch>'
> -- Luc Van Oostenryck