All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: git@vger.kernel.org
Subject: Re: `git-rev-parse master` not referred to by any ref?
Date: Sun, 26 Aug 2007 10:06:45 -0400	[thread overview]
Message-ID: <20070826140645.GC20243@fieldses.org> (raw)
In-Reply-To: <20070826135251.GB20243@fieldses.org>

On Sun, Aug 26, 2007 at 09:52:51AM -0400, J. Bruce Fields wrote:
> On Sun, Aug 26, 2007 at 09:45:21AM -0400, J. Bruce Fields wrote:
> > Any idea how I got into this situation?:
> > 
> > 	git$ git rev-parse master
> > 	warning: refname 'master' is ambiguous.
> > 	407c0c87e15b3cf60347f4fc0bcdb4d239de4163
> > 	~/local/git$ git for-each-ref | grep master
> > 	32ebe844c689d6e13e9875a0feefedca8dc1c6eb commit refs/heads/master
> > 	e413074f1293e907d94af99330f0dd632a78b01f commit refs/remotes/linux-nfs/master
> > 	0058a33a8eb5a8bfcfc5f5e769a2517cff4b73f1 commit refs/remotes/origin/master
> > 	git$ git for-each-ref | grep 407c0
> > 	git$ 
> 
> Oops, found it:
> 
> 	git$ cat .git/master
> 	407c0c87e15b3cf60347f4fc0bcdb4d239de4163

(Somebody on irc pointed out that

	git update-ref master 407c0c87e15b3cf60347f4fc0bcdb4d239de4163

The file's dated a couple weeks ago, so I don't remember, but I can
easily imagine that I could have typed that assuming it'd update
.git/refs/heads/master.  OK!)

--b.

  reply	other threads:[~2007-08-26 14:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-26 13:45 `git-rev-parse master` not referred to by any ref? J. Bruce Fields
2007-08-26 13:52 ` J. Bruce Fields
2007-08-26 14:06   ` J. Bruce Fields [this message]
2007-08-26 21:26     ` Junio C Hamano
2007-08-26 22:28       ` Shawn O. Pearce
2007-08-26 22:36       ` J. Bruce Fields

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=20070826140645.GC20243@fieldses.org \
    --to=bfields@fieldses.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.