From: Nicolas Bock <nbock@lanl.gov>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: error: cannot lock ref 'refs/remotes/origin/*'
Date: Tue, 17 Jun 2008 08:22:00 -0600 [thread overview]
Message-ID: <1213712520.6400.1.camel@localhost> (raw)
In-Reply-To: <alpine.DEB.1.00.0806171140470.6439@racer>
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
This is what I get:
$ git show-ref
a4995ae293fd95697a643cd3ea45585ecc38a19d refs/heads/ACT
3378ccb42c22740b7fcc240ffa0e4f798b8acf1f refs/heads/master
78e33155a0ab4ab0acba4c64758681fe99f1c5ca refs/heads/nick
ef66b3aa74b8c1edb55161e01a99dee7cf9edaa3 refs/remotes/origin/*
3378ccb42c22740b7fcc240ffa0e4f798b8acf1f refs/remotes/origin/master
in what sense is this ref "bogus"? Is it syntactically incorrect?
On Tue, 2008-06-17 at 11:41 +0100, Johannes Schindelin wrote:
> Hi,
>
> On Mon, 16 Jun 2008, Nicolas Bock wrote:
>
> > > $ git gc
> > > error: cannot lock ref 'refs/remotes/origin/*'
> > > error: failed to run reflog
>
> This is a bogus ref name. Hrm. Can you look with "git show-ref" if you
> have (by some funny accident) an invalid ref there?
>
> Ciao,
> Dscho
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-06-17 14:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 16:53 error: cannot lock ref 'refs/remotes/origin/*' Nicolas Bock
2008-06-17 1:47 ` Nicolas Bock
2008-06-17 10:41 ` Johannes Schindelin
2008-06-17 14:22 ` Nicolas Bock [this message]
2008-06-17 14:29 ` Johan Herland
2008-06-17 15:49 ` Nicolas Bock
2008-06-17 19:09 ` Jakub Narebski
2008-06-17 21:00 ` Nicolas Bock
2008-06-17 14:46 ` Johannes Schindelin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1213712520.6400.1.camel@localhost \
--to=nbock@lanl.gov \
--cc=Johannes.Schindelin@gmx.de \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).