{"thread":{"id":"16496","subject":"How to know where a reference name comes from?","startedAt":"2008-11-27T09:18:30Z","lastAt":"2008-11-27T09:47:11Z","messageCount":2,"participants":["Matthieu Moy","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"96612","messageId":"vpqk5ap5xy1.fsf@bauges.imag.fr","threadId":"16496","inReplyTo":null,"subject":"How to know where a reference name comes from?","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@imag.fr","sentAt":"2008-11-27T09:18:30Z","receivedAt":"2008-11-27T09:18:30Z","isPatch":false,"sender":{"key":"git@matthieu-moy.fr","avatar":"https://avatars.githubusercontent.com/u/14709?v=4"},"body":"Hi,\n\nI faced a simple problem: on a repository, doing almost anything with\nthe reference \"git-svn\" complained about ambiguous reference. I know I\nhave a remotes/git-svn branch, but I didn't know what the other\nreference could be.\n\nI didn't find a command telling me _why_ this \"git-svn\" was ambiguous.\nI'd have loved a\n\n$ git rev-parse --all-symbolic-full-names git-svn\n\nor so, but I couldn't find one.\n\nDid I miss anything obvious? (not that the problem was big, I'm just\ncurious).\n\n(I ended up doing \"strace -e open git rev-parse git-svn\", and found\nout I had a .git/git-svn file lying around)\n\nThanks,\n\n-- \nMatthieu\n"},{"id":"96615","messageId":"7v4p1tbiw0.fsf@gitster.siamese.dyndns.org","threadId":"16496","inReplyTo":"vpqk5ap5xy1.fsf@bauges.imag.fr","subject":"Re: How to know where a reference name comes from?","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2008-11-27T09:47:11Z","receivedAt":"2008-11-27T09:47:11Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Matthieu Moy <Matthieu.Moy@imag.fr> writes:\n\n> (I ended up doing \"strace -e open git rev-parse git-svn\", and found\n> out I had a .git/git-svn file lying around)\n\nThis has been proposed for a couple of times now but I think it might be\ntime to start insisting on a ref directly underneath $GIT_DIR to be in all\ncaps (plus underscore) to avoid issues like this while still allowing\ntraditional MERGE_HEAD, ORIG_HEAD and friends.\n"}]}