git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: error: cannot lock ref 'refs/remotes/origin/*'

From
Nicolas Bock <nbock@lanl.gov>
Date
Jun 17, 2008, 15:49 UTC
Message-ID
<1213717788.13390.2.camel@localhost>
In-Reply-To
<200806171629.06570.johan@herland.net>
I guess I don't understand refs. I figured that since I have
remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
set, I should have a ref refs/remotes/origin/* as well.
On Tue, 2008-06-17 at 16:29 +0200, Johan Herland wrote:
Show 18 quoted lines
> On Tuesday 17 June 2008, Nicolas Bock wrote:
> > 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?
> 
> Yes, According to "man git-check-ref-format", asterisk is NOT allowed in 
> a ref name.
> 
> 
> ...Johan
>
Previous: Johan HerlandNext: Jakub Narebski
Message 6 of 9 in “error: cannot lock ref 'refs/remotes/origin/*'”
  1. Nicolas BockJun 16, 2008
  2. Nicolas BockJun 17, 2008
  3. Johannes SchindelinJun 17, 2008
  4. Nicolas BockJun 17, 2008
  5. Johan HerlandJun 17, 2008
  6. Nicolas BockJun 17, 2008
  7. Jakub NarebskiJun 17, 2008
  8. Nicolas BockJun 17, 2008
  9. Johannes SchindelinJun 17, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.