From: Nicolas Bock <nbock@lanl.gov>
To: Johan Herland <johan@herland.net>
Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: error: cannot lock ref 'refs/remotes/origin/*'
Date: Tue, 17 Jun 2008 09:49:48 -0600 [thread overview]
Message-ID: <1213717788.13390.2.camel@localhost> (raw)
In-Reply-To: <200806171629.06570.johan@herland.net>
[-- Attachment #1: Type: text/plain, Size: 865 bytes --]
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:
> 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
>
[-- 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 15:50 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
2008-06-17 14:29 ` Johan Herland
2008-06-17 15:49 ` Nicolas Bock [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1213717788.13390.2.camel@localhost \
--to=nbock@lanl.gov \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=johan@herland.net \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.