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. - 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
