From: Ben Tebulin <nntp.20.jexpert@spamgourmet.com>
To: git@vger.kernel.org
Subject: Git on SVN: space characters in branch names
Date: Tue, 06 Mar 2012 18:31:27 +0100 [thread overview]
Message-ID: <jj5hl0$7dm$1@dough.gmane.org> (raw)
Hi! I'm trying to move to Git on top of Subversion in my company
environment using Cygwin/Git 1.7.9. Therefore I'm trying to clone
a set of SVN repositories.
The SVN repository I'm trying to clone contains a commit, where a
branch was accidentally named "1.1.x _M1":
git svn clone -s https://svnserver/repository project.git \
--ignore-path=".*(?:1.1.x _M1|1.1.x%20_M1)"
This skips the initial commit, but still stumbles on the rename commit:
Found possible branch point: \
https://svnserver/repository/branches/1.1.x _M1 => \
https://svnserver/repository/branches/1.1.x_M1, 2374
fatal: Not a valid object name refs/remotes/1.1.x _M1
cat-file commit refs/remotes/1.1.x _M1: command returned error: 128
Do I have to ignore the branch completely?
Thanks
- Ben
reply other threads:[~2012-03-06 17:35 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='jj5hl0$7dm$1@dough.gmane.org' \
--to=nntp.20.jexpert@spamgourmet.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).