From: Jeenu V <jeenuv@gmail.com>
To: git@vger.kernel.org
Subject: Re: Ambiguous ref names
Date: Fri, 11 Dec 2009 13:33:09 +0530 [thread overview]
Message-ID: <5195c8760912110003u6deabf7ey44b1f2dd448ce7fe@mail.gmail.com> (raw)
In-Reply-To: <5195c8760911200355x1aff9781l848f974c9f09f416@mail.gmail.com>
On Fri, Nov 20, 2009 at 5:25 PM, Jeenu V <jeenuv@gmail.com> wrote:
>
> On Fri, Nov 20, 2009 at 4:29 PM, Junio C Hamano <gitster@pobox.com> wrote:
> > Jeenu V <jeenuv@gmail.com> writes:
> >
> >> On Fri, Nov 20, 2009 at 3:56 PM, Junio C Hamano <gitster@pobox.com> 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
prev parent reply other threads:[~2009-12-11 8:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 10:18 Ambiguous ref names Jeenu V
2009-11-20 10:26 ` Junio C Hamano
2009-11-20 10:48 ` Jeenu V
2009-11-20 10:59 ` Junio C Hamano
2009-11-20 11:55 ` Jeenu V
2009-12-11 8:03 ` Jeenu V [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5195c8760912110003u6deabf7ey44b1f2dd448ce7fe@mail.gmail.com \
--to=jeenuv@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox