Skip to content

Allow multiple --tags options #34

Open
bulletmark opened this Issue Dec 24, 2011 · 12 comments

6 participants

@bulletmark

The svn repo I am trying to migrate has 2 "tags" directories. The "git svn clone" command allows specification of multiple --tags options to handle this but unfortunately svn2git does not accept this.

@nirvdrum
Owner

I'll have to double-check, but I don't think git-svn allows that. And svn2git is mostly just a nice wrapper around git-svn.

@bulletmark

My git version 1.7.8.1 git help svn says "You can specify more than one --tags and/or --branches options, in case your Subversion repository places tags or branches under multiple paths."

@nirvdrum
Owner

Nifty. I was unaware of that. Did you happen to pull together something that would work? If so, a pull request would be much appreciated.

@bulletmark

I ended up hacking up my own shell script, based initially on http://github.com/JohnAlbin/git-svn-migrate, to do what I wanted. Not much use to you sorry.

@lbreuss
lbreuss commented May 24, 2012

I've got the fix for that. It processes multiple --tags and --branches and forwards that to git-svn.

I'm a noob to Github. I'll investigate how to fork svn2git and send you a pull request once I've pushed my fix.

@nirvdrum
Owner

Awesome. If you push from a branch, you can go to that branch in GitHub to issue the pull request.

@lbreuss
lbreuss commented May 24, 2012

Awesome! I like the capabilities of github. It even shows my pull request here, just because I referened this issue in the request.

@sajidali

When is this issue going to be fixed, I need to convert an svn project with multiple tags directories.

@JeromeGill

There has been a PR for this issue open for 2 years. We have hit this problem also, any chance of a merge?

@Zitrax
Zitrax commented Jan 11, 2016

I hit this too, is this maintained still ? Last commit on master April 2015 while there are quite a lot of issues and pull requests.

@nirvdrum
Owner

The project is maintained, it's just nearly every PR I receive breaks something on someone else or adds a pet feature that I don't want to include. What PR addresses this issue? I'll take another look.

@Zitrax
Zitrax commented Jan 11, 2016

@nirvdrum Thanks - good to know.

I tried the PR referenced above after squashing and rebasing on current master and it seemed to work for me. Here is my commit: Zitrax@1005cbd

However I have not verified the output very carefully yet - for example I am curious how it would handle multiple tags/branches with the same name.

And I noticed that there were more branches and tags than I expected. When I looked at them they were branches and tags that had been deleted in svn. I guess that is expected (?) - but I would have to think a bit if that pollution is really what I want since we have a lot of them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.