From: Michael Lai <myllai@gmail.com>
To: git@vger.kernel.org
Subject: git-svn does not support intermediate directories?
Date: Tue, 3 Mar 2009 17:43:47 -0800 [thread overview]
Message-ID: <21fc26450903031743x4beda8a3i835ecbd428817070@mail.gmail.com> (raw)
Hey all,
After spending some hours struggling with git svn, it would appear
that it does not support svn projects stored in paths similar to
"http://foo.com/svn/repos/bar/myproject", where "myproject" uses the
standard SVN tags/trunk/branches layout. I'm currently using git
1.6.1, though I tried this with 1.6.2-rc2 as well. The resulting
.git/config looks something like this:
[svn-remote "svn"]
url = http://foo.com/svn/repos/bar
fetch = myproject/trunk:refs/remotes/trunk
branches = bar/myproject/branches/*:refs/remotes/*
tags = bar/myproject/tags/*:refs/remotes/tags/*
Yes, that's a redundant "bar" directory under "branches =" and "tags
=". The issue seems to lie in git-svn doing something intelligent to
extract the appropriate trunk directory. For the branches and tags,
however, it just takes the full URL and removes the repository root
(http://foo.com/svn/repos/bar) to produce "bar/myproject/{branches,
tags}/*". The second effect is that "git svn fetch" will run but exit
quietly without actually pulling anything from the repository. I
tracked down an existing thread on the mailing list from a while ago
(Feb 4th, title of "git-svn doesn't fetch anything"), but there was no
resolution.
There is a quick workaround, which was to make this change to match_paths:
< $self->{path_regex} ||= qr/^\/\Q$self->{path}\E\//;
---
> $self->{path_regex} ||= qr/\/\Q$self->{path}\E\//;
The additional "bar" directory gets pulled in when git-svn tries to
determine what paths to pull down, and tries to match
"/myproject/trunk" to "/bar/myproject/trunk". I've merely put a
band-aid on the situation. My perl is rudimentary at best, or I'd
have spent additional time to try to put in a "proper" patch, but was
wondering if anyone else had run into this problem and would be
willing to put in a fix (or point me in the right direction, that
works too).
Thanks,
Mike
next reply other threads:[~2009-03-04 1:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 1:43 Michael Lai [this message]
2009-03-04 4:30 ` git-svn does not support intermediate directories? Tim Stoakes
2009-03-06 0:12 ` [RFC PATCH] " Michael Lai
2009-03-08 4:43 ` Eric Wong
2009-03-09 21:02 ` Michael Lai
2009-03-09 21:54 ` Eric Wong
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=21fc26450903031743x4beda8a3i835ecbd428817070@mail.gmail.com \
--to=myllai@gmail.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).