From: "Brecht Machiels" <brecht+gmane@mos6581.org>
To: git@vger.kernel.org
Subject: git-svn and spaces in branch names
Date: Fri, 22 Jun 2012 19:57:26 +0200 [thread overview]
Message-ID: <op.wgbf51qi518yxf@krusty> (raw)
Hello,
I believe I have run into a bug in git-svn. I'm trying to clone a large
subversion repository. It's layout looks roughly like this:
project/
1.0/
branches/
some_feature
anotherFeature
tags/
1.0 IR1
1.0 IR2
merge_tags/
...
daily_builds/
...
1.1/
...
I created a custom git-svn configuration to map the branches and tags to
git remotes. As the tags dir inside each version dir contains the
merge_tags and daily_builds folders, I have manually specified the tags to
match:
branches = 1.0/tags/{1.0 IR1,1.0 IR2}:refs/remotes/tags/1.0/*
branches = 1.0/tags/daily_builds/*:refs/remotes/daily_builds/1.0/*
branches = 1.0/tags/merge_tags/*:refs/remotes/merge_tags/1.0/*
The {} operator seems to fail on entries containing spaces. The tags seems
to be cloned correctly, however, git-svn chokes on accessing them. I'm not
at work now, so I can't paste the exact error, but it included the
following error message:
fatal: Not a valid object name: 'remotes/tags/1.0/1.0%20IR1'.
I noticed this difference:
".git/refs/remotes/tags/1.0/1.0%20IR1" versus
".git/refs/svn/remotes/tags/1.0/1.0 IR1" (space versus HTML entity)
In an attempt to sidestep the issue, I tried the following configuration:
branches = 1.0/tags/*:refs/remotes/tags/1.0/*
... and additionally using --ignore-paths on the daily_builds and
merge_tags paths (I can take care of those later). This approach doesn't
result in errors, so the problem must lie with the {} construct.
If any more information is required, I can provide it after the weekend.
Cheers,
Brecht
reply other threads:[~2012-06-24 16:05 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=op.wgbf51qi518yxf@krusty \
--to=brecht+gmane@mos6581.org \
--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).