{"thread":{"id":"17928","subject":"git-svn and branches with spaces","startedAt":"2009-02-20T23:26:04Z","lastAt":"2009-02-20T23:26:04Z","messageCount":1,"participants":["Dan Fabulich"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"105667","messageId":"alpine.OSX.1.10.0902201515470.1576@sfimac.local","threadId":"17928","inReplyTo":null,"subject":"git-svn and branches with spaces","fromName":"Dan Fabulich","fromEmail":"dan@fabulich.com","sentAt":"2009-02-20T23:26:04Z","receivedAt":"2009-02-20T23:26:04Z","isPatch":false,"sender":{"key":"dan@fabulich.com","avatar":"https://gravatar.com/avatar/884cee2af623b7675bebdd7b70b13dcb8423150d8f137ec0841859b80a21cd05?d=mp&s=160"},"body":"\nAs others have noticed, git-svn can't handle branches with spaces.\n\nhttp://markmail.org/message/r56iyw3vubwbycgt\n\nTurns out that there is a possible workaround: thiago's \nsvn-all-fast-export tool is super super configurable, allowing you to work \naround evil branch names by modifying your matching rules.\n\nhttp://repo.or.cz/w/svn-all-fast-export.git\n\nI made rules like this:\n\nmatch /branches/crazy branch with spaces/\n   repository myproject\n   branch crazy_branch_with_spaces\nend match\n\nmatch /branches/([^/]+)/\n   repository myproject\n   branch \\1\nend match\n\nSince the rules apply in order, the evil branch name matched before the \ncatch-all matcher, fixing my problem.\n\nAnd it doesn't hurt that svn-all-fast-export is at least an order of \nmagnitude faster than git-svn clone...  If you find that git-svn is too \nslow, I strongly recommend svn-all-fast-export.git for performance alone!\n\n-Dan\n"}]}