# git-svn problems with branches containing spaces 4 messages from 2007-06-27 to 2007-07-11. Participants: Ewald, Robert, Gerrit Pape, Jan Hudec, Eric Wong. Thread: https://gitlist.dev/t/8745 ## Ewald, Robert, 2007-06-27 06:53 Subject: git-svn problems with branches containing spaces Message-ID: <3F225D5F64550C4AA5F23286244275D4298C84@srvkrsexc07.nov.com> URL: https://gitlist.dev/e/3F225D5F64550C4AA5F23286244275D4298C84%40srvkrsexc07.nov.com ``` Hello, 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. Best regards Robert Ewald PS. Please CC me, I am not subscribed. ``` ## Gerrit Pape, 2007-07-10 13:42 Subject: Re: git-svn problems with branches containing spaces Message-ID: <20070710134236.2870.qmail@986bac8bfff25d.315fe32.mid.smarden.org> URL: https://gitlist.dev/e/20070710134236.2870.qmail%40986bac8bfff25d.315fe32.mid.smarden.org In-Reply-To: <3F225D5F64550C4AA5F23286244275D4298C84@srvkrsexc07.nov.com> ``` 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. Thanks, Gerrit. ``` ## Jan Hudec, 2007-07-10 18:33 Subject: Re: git-svn problems with branches containing spaces Message-ID: <20070710183328.GB4808@efreet.light.src> URL: https://gitlist.dev/e/20070710183328.GB4808%40efreet.light.src In-Reply-To: <20070710134236.2870.qmail@986bac8bfff25d.315fe32.mid.smarden.org> ``` On Tue, Jul 10, 2007 at 13:42:35 +0000, Gerrit Pape 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. It depends on whether it's OK for git to have refs with funny characters in them. If it is, than the patch would be a fix. If not, than the escaping the patch removes needs to be added to all other places that have any business with refs. -- Jan 'Bulb' Hudec ``` ## Eric Wong, 2007-07-11 08:29 Subject: Re: git-svn problems with branches containing spaces Message-ID: <20070711082907.GA29676@muzzle> URL: https://gitlist.dev/e/20070711082907.GA29676%40muzzle In-Reply-To: <20070710134236.2870.qmail@986bac8bfff25d.315fe32.mid.smarden.org> ``` Gerrit Pape 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 ```