On Fri, Nov 20, 2009 at 5:25 PM, Jeenu V <jeenuv@xxxxxxxxx> wrote: > > On Fri, Nov 20, 2009 at 4:29 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > > Jeenu V <jeenuv@xxxxxxxxx> writes: > > > >> On Fri, Nov 20, 2009 at 3:56 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > >>> [...] > >>> It could be that you have a tag and a branch that are both named a.b.c, > >>> though. > >> > >> Hm, right. But I'm getting this from an existing local repo of mine. I > >> can't see any tags; 'git tag -l' is empty. Is there any more info that > >> I can provide? > > > > man git-for-each-ref? > > It does list all refs that I know of, but I don't see any duplicate entries. Ah, I think I get what happened here: I had used git update-ref, which turned out to be used wrongly. My intention was to update a.b.c to a new ref, but I used it 'git update-ref XXXXXX', rather than 'git update-ref refs/heads/a.b.c XXXXXX'. The wrong usage created .git/a.b.c and I guess this was causing the warning. -- :J -- 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