From: Dan Fabulich <dan@fabulich.com>
To: git@vger.kernel.org
Subject: git-svn and branches with spaces
Date: Fri, 20 Feb 2009 15:26:04 -0800 (PST) [thread overview]
Message-ID: <alpine.OSX.1.10.0902201515470.1576@sfimac.local> (raw)
As others have noticed, git-svn can't handle branches with spaces.
http://markmail.org/message/r56iyw3vubwbycgt
Turns out that there is a possible workaround: thiago's
svn-all-fast-export tool is super super configurable, allowing you to work
around evil branch names by modifying your matching rules.
http://repo.or.cz/w/svn-all-fast-export.git
I made rules like this:
match /branches/crazy branch with spaces/
repository myproject
branch crazy_branch_with_spaces
end match
match /branches/([^/]+)/
repository myproject
branch \1
end match
Since the rules apply in order, the evil branch name matched before the
catch-all matcher, fixing my problem.
And it doesn't hurt that svn-all-fast-export is at least an order of
magnitude faster than git-svn clone... If you find that git-svn is too
slow, I strongly recommend svn-all-fast-export.git for performance alone!
-Dan
reply other threads:[~2009-02-20 23:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.OSX.1.10.0902201515470.1576@sfimac.local \
--to=dan@fabulich.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).