From: Eric Wong <normalperson@yhbt.net>
To: git@vger.kernel.org
Cc: "Ewald, Robert" <Robert.Ewald@nov.com>
Subject: Re: git-svn problems with branches containing spaces
Date: Wed, 11 Jul 2007 01:29:07 -0700 [thread overview]
Message-ID: <20070711082907.GA29676@muzzle> (raw)
In-Reply-To: <20070710134236.2870.qmail@986bac8bfff25d.315fe32.mid.smarden.org>
Gerrit Pape <pape@smarden.org> wrote:
> On Wed, Jun 27, 2007 at 08:53:06AM +0200, Ewald, Robert wrote:
> > As I have reported yesterday on IRC, git-svn has problems with branches
> > containing spaces.
> > I get the following message, when I want to clone from the repository
> > containing a branch with a space.
> > Cloning until the revision the branch is created everything works fine.
> >
> > fatal: refs/remotes/Modbus Error Limit Fix: cannot lock the ref
> > update-ref -m r1897 refs/remotes/Modbus Error Limit Fix
> > ff0819c8e9c97c24e9865bc868c503fd9b64f980: command returned error: 128
> >
> > Thanks for your help.
>
> Hi, the same problem has been reported some time ago through
> http://bugs.debian.org/430518
>
> There's a patch attached to the report, but from a first glance, I don't
> think it's the solution.
That patch is definitely not a correct solution. If another branch came
along with the same name as an automatically renamed one, it would break
things badly.
I started working on a patch that allowed the user to interactively
specify replacement branch names, but never got around to finishing
it:
http://permalink.gmane.org/gmane.comp.version-control.git/45651
--
Eric Wong
prev parent reply other threads:[~2007-07-11 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 6:53 git-svn problems with branches containing spaces Ewald, Robert
2007-07-10 13:42 ` Gerrit Pape
2007-07-10 18:33 ` Jan Hudec
2007-07-11 8:29 ` Eric Wong [this message]
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=20070711082907.GA29676@muzzle \
--to=normalperson@yhbt.net \
--cc=Robert.Ewald@nov.com \
--cc=git@vger.kernel.org \
/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).