git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Lars Hjemli" <hjemli@gmail.com>
To: "Eric Wong" <normalperson@yhbt.net>
Cc: "James Peach" <jamespeach@mac.com>, git@vger.kernel.org
Subject: Re: git-svn "cannot lock ref" error during fetch
Date: Thu, 7 Jun 2007 08:54:00 +0200	[thread overview]
Message-ID: <8c5c35580706062354g5b19e4b8x43d211f634a8583b@mail.gmail.com> (raw)
In-Reply-To: <20070607063158.GA2809@muzzle>

On 6/7/07, Eric Wong <normalperson@yhbt.net> wrote:
> James Peach <jamespeach@mac.com> wrote:
> > update-ref -m r13726 refs/remotes/tags/project-92~9
> > 950638ff72acc278156a0d55baafbabb43f2b772: command returned error: 128
> >
> > Some amount of searching failed to turn up any hints on what this
> > error means or how I can work around it. I'd appreciate any advice ...
>
> Is there a tag actually named "project-92~9"?  If so, it's
> an invalid branch name for git.  I started working on a way
> around it by mapping new names to it, but haven't gotten around to
> finishing it....
>

fwiw: a similar error occurs when a svn tag-/branchname contains
spaces. The culprit seems to be $self->refname in

		command_noisy('update-ref', '-m', "r$rev",
		              $self->refname, $commit);

in rev_db_set()

--
larsh

  reply	other threads:[~2007-06-07  6:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06 17:17 git-svn "cannot lock ref" error during fetch James Peach
2007-06-07  6:31 ` Eric Wong
2007-06-07  6:54   ` Lars Hjemli [this message]
2007-06-07 15:37   ` James Peach
2007-06-09 20:06     ` Eric Wong
2007-06-13 23:07       ` James Peach

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=8c5c35580706062354g5b19e4b8x43d211f634a8583b@mail.gmail.com \
    --to=hjemli@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jamespeach@mac.com \
    --cc=normalperson@yhbt.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 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 NNTP newsgroup(s).