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@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html
Attachment:
signature.asc
Description: This is a digitally signed message part
