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, 21:00 UTC
Message-ID
<1213736407.2490.9.camel@localhost>
In-Reply-To
<m3fxrbop4g.fsf@localhost.localdomain>
Thanks, that explains it..
nick
On Tue, 2008-06-17 at 12:09 -0700, Jakub Narebski wrote:
Show 13 quoted lines
> Nicolas Bock <nbock@lanl.gov> writes:
> 
> > 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.
> 
> The above is _globbing_ refspec, it means that it maps 
> "refs/heads/<name>" branch in remote repository to 
> "refs/remotes/origin/<name>" remote-tracking branch in local
> repository.
>
Previous: Jakub NarebskiNext: Johannes Schindelin
Message 8 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.