git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 7, 2017, 15:53 UTC
Message-ID
<xmqqd19cckfw.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20170707123727.dgd5rub2ycrg525y@ltop.local>
Luc Van Oostenryck <luc.vanoostenryck@gmail.com> 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?

Show 6 quoted lines
> Strangely, trying a second time, succeed:
> 	$ git co <abranch>
> 	Previous HEAD position was ...
> 	Switched to branch '<abranch>'
>
> -- Luc Van Oostenryck
Previous: Luc Van OostenryckNext: Luc Van Oostenryck
Message 2 of 5 in “bug during checkout of remote branch and uncommited changes ?”
  1. Luc Van OostenryckJul 7, 2017
  2. Junio C HamanoJul 7, 2017
  3. Luc Van OostenryckJul 7, 2017
  4. Junio C HamanoJul 7, 2017
  5. Luc Van OostenryckJul 7, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.