{"thread":{"id":"30889","subject":"git-svn and spaces in branch names","startedAt":"2012-06-22T17:57:26Z","lastAt":"2012-06-22T17:57:26Z","messageCount":1,"participants":["Brecht Machiels"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"194168","messageId":"op.wgbf51qi518yxf@krusty","threadId":"30889","inReplyTo":null,"subject":"git-svn and spaces in branch names","fromName":"Brecht Machiels","fromEmail":"brecht+gmane@mos6581.org","sentAt":"2012-06-22T17:57:26Z","receivedAt":"2012-06-22T17:57:26Z","isPatch":false,"sender":{"key":"brecht+gmane@mos6581.org","avatar":null},"body":"Hello,\n\nI believe I have run into a bug in git-svn. I'm trying to clone a large  \nsubversion repository. It's layout looks roughly like this:\n\nproject/\n   1.0/\n     branches/\n       some_feature\n       anotherFeature\n     tags/\n       1.0 IR1\n       1.0 IR2\n       merge_tags/\n         ...\n       daily_builds/\n         ...\n   1.1/\n     ...\n\nI created a custom git-svn configuration to map the branches and tags to  \ngit remotes. As the tags dir inside each version dir contains the  \nmerge_tags and daily_builds folders, I have manually specified the tags to  \nmatch:\n\n   branches = 1.0/tags/{1.0 IR1,1.0 IR2}:refs/remotes/tags/1.0/*\n   branches = 1.0/tags/daily_builds/*:refs/remotes/daily_builds/1.0/*\n   branches = 1.0/tags/merge_tags/*:refs/remotes/merge_tags/1.0/*\n\nThe {} operator seems to fail on entries containing spaces. The tags seems  \nto be cloned correctly, however, git-svn chokes on accessing them. I'm not  \nat work now, so I can't paste the exact error, but it included the  \nfollowing error message:\nfatal: Not a valid object name: 'remotes/tags/1.0/1.0%20IR1'.\n\nI noticed this difference:\n     \".git/refs/remotes/tags/1.0/1.0%20IR1\" versus\n\".git/refs/svn/remotes/tags/1.0/1.0 IR1\" (space versus HTML entity)\n\nIn an attempt to sidestep the issue, I tried the following configuration:\n\n   branches = 1.0/tags/*:refs/remotes/tags/1.0/*\n\n... and additionally using --ignore-paths on the daily_builds and  \nmerge_tags paths (I can take care of those later). This approach doesn't  \nresult in errors, so the problem must lie with the {} construct.\n\nIf any more information is required, I can provide it after the weekend.\n\nCheers,\nBrecht\n"}]}