{"thread":{"id":"8745","subject":"git-svn problems with branches containing spaces","startedAt":"2007-06-27T06:53:06Z","lastAt":"2007-07-11T08:29:07Z","messageCount":4,"participants":["Ewald, Robert","Gerrit Pape","Jan Hudec","Eric Wong"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"45893","messageId":"3F225D5F64550C4AA5F23286244275D4298C84@srvkrsexc07.nov.com","threadId":"8745","inReplyTo":null,"subject":"git-svn problems with branches containing spaces","fromName":"Ewald, Robert","fromEmail":"robert.ewald@nov.com","sentAt":"2007-06-27T06:53:06Z","receivedAt":"2007-06-27T06:53:06Z","isPatch":false,"sender":{"key":"robert.ewald@nov.com","avatar":null},"body":"Hello,\n\nAs I have reported yesterday on IRC, git-svn has problems with branches\ncontaining spaces.\nI get the following message, when I want to clone from the repository\ncontaining a branch with a space.\nCloning until the revision the branch is created everything works fine.\n\nfatal: refs/remotes/Modbus Error Limit Fix: cannot lock the ref\nupdate-ref -m r1897 refs/remotes/Modbus Error Limit Fix\nff0819c8e9c97c24e9865bc868c503fd9b64f980: command returned error: 128\n\nThanks for your help.\n\nBest regards\n\nRobert Ewald\n\nPS. Please CC me, I am not subscribed.\n"},{"id":"46940","messageId":"20070710134236.2870.qmail@986bac8bfff25d.315fe32.mid.smarden.org","threadId":"8745","inReplyTo":"3F225D5F64550C4AA5F23286244275D4298C84@srvkrsexc07.nov.com","subject":"Re: git-svn problems with branches containing spaces","fromName":"Gerrit Pape","fromEmail":"pape@smarden.org","sentAt":"2007-07-10T13:42:35Z","receivedAt":"2007-07-10T13:42:35Z","isPatch":false,"sender":{"key":"pape@smarden.org","avatar":"https://avatars.githubusercontent.com/u/143170252?v=4"},"body":"On Wed, Jun 27, 2007 at 08:53:06AM +0200, Ewald, Robert wrote:\n> As I have reported yesterday on IRC, git-svn has problems with branches\n> containing spaces.\n> I get the following message, when I want to clone from the repository\n> containing a branch with a space.\n> Cloning until the revision the branch is created everything works fine.\n> \n> fatal: refs/remotes/Modbus Error Limit Fix: cannot lock the ref\n> update-ref -m r1897 refs/remotes/Modbus Error Limit Fix\n> ff0819c8e9c97c24e9865bc868c503fd9b64f980: command returned error: 128\n> \n> Thanks for your help.\n\nHi, the same problem has been reported some time ago through\n http://bugs.debian.org/430518\n\nThere's a patch attached to the report, but from a first glance, I don't\nthink it's the solution.\n\nThanks, Gerrit.\n"},{"id":"46977","messageId":"20070710183328.GB4808@efreet.light.src","threadId":"8745","inReplyTo":"20070710134236.2870.qmail@986bac8bfff25d.315fe32.mid.smarden.org","subject":"Re: git-svn problems with branches containing spaces","fromName":"Jan Hudec","fromEmail":"bulb@ucw.cz","sentAt":"2007-07-10T18:33:28Z","receivedAt":"2007-07-10T18:33:28Z","isPatch":false,"sender":{"key":"bulb@ucw.cz","avatar":null},"body":"On Tue, Jul 10, 2007 at 13:42:35 +0000, Gerrit Pape wrote:\n> On Wed, Jun 27, 2007 at 08:53:06AM +0200, Ewald, Robert wrote:\n> > As I have reported yesterday on IRC, git-svn has problems with branches\n> > containing spaces.\n> > I get the following message, when I want to clone from the repository\n> > containing a branch with a space.\n> > Cloning until the revision the branch is created everything works fine.\n> > \n> > fatal: refs/remotes/Modbus Error Limit Fix: cannot lock the ref\n> > update-ref -m r1897 refs/remotes/Modbus Error Limit Fix\n> > ff0819c8e9c97c24e9865bc868c503fd9b64f980: command returned error: 128\n> > \n> > Thanks for your help.\n> \n> Hi, the same problem has been reported some time ago through\n> http://bugs.debian.org/430518\n> \n> There's a patch attached to the report, but from a first glance, I don't\n> think it's the solution.\n\nIt depends on whether it's OK for git to have refs with funny characters in\nthem. If it is, than the patch would be a fix. If not, than the escaping the\npatch removes needs to be added to all other places that have any business\nwith refs.\n\n-- \n\t\t\t\t\t\t Jan 'Bulb' Hudec \n"},{"id":"47015","messageId":"20070711082907.GA29676@muzzle","threadId":"8745","inReplyTo":"20070710134236.2870.qmail@986bac8bfff25d.315fe32.mid.smarden.org","subject":"Re: git-svn problems with branches containing spaces","fromName":"Eric Wong","fromEmail":"normalperson@yhbt.net","sentAt":"2007-07-11T08:29:07Z","receivedAt":"2007-07-11T08:29:07Z","isPatch":false,"sender":{"key":"e@80x24.org","avatar":null},"body":"Gerrit Pape wrote:\n> On Wed, Jun 27, 2007 at 08:53:06AM +0200, Ewald, Robert wrote:\n> > As I have reported yesterday on IRC, git-svn has problems with branches\n> > containing spaces.\n> > I get the following message, when I want to clone from the repository\n> > containing a branch with a space.\n> > Cloning until the revision the branch is created everything works fine.\n> > \n> > fatal: refs/remotes/Modbus Error Limit Fix: cannot lock the ref\n> > update-ref -m r1897 refs/remotes/Modbus Error Limit Fix\n> > ff0819c8e9c97c24e9865bc868c503fd9b64f980: command returned error: 128\n> > \n> > Thanks for your help.\n> \n> Hi, the same problem has been reported some time ago through\n> http://bugs.debian.org/430518\n> \n> There's a patch attached to the report, but from a first glance, I don't\n> think it's the solution.\n\nThat patch is definitely not a correct solution. If another branch came\nalong with the same name as an automatically renamed one, it would break\nthings badly.\n\nI started working on a patch that allowed the user to interactively\nspecify replacement branch names, but never got around to finishing\nit:\n\nhttp://permalink.gmane.org/gmane.comp.version-control.git/45651\n\n-- \nEric Wong\n"}]}