How to clone a nonstandard svn repo to git?

Question

I try to clone a svn repo to git, but some of the branches are in the svn root dir like follows.

I've tried

$ git clone svn://url/svn-root -T trunk -b branches -b branch1 -b branch2

and

$ git clone svn://url/svn-root -T trunk -b branches -b .

Both are failed to clone the branch1 and branch2 correctly. Please help.

svn-root
├── branch1
├── branch2
├── branches
│   ├── branch3
│   └── branch4
└── trunk

Community · Accepted Answer · 2017-05-23 10:30:28Z

6

One interesting tool, mentioned in GitMinutes Episode 20, is SubGit, a plugin for Atalssian Stash (which isn't free, but you can try it for free).
You can know much more about SubGit in "GitMinutes #22: Alexander Kitaev about SubGit".

It is designed to managed unconventional svn repo layout.

Dmitry Pavlenko comments:

you should enter in the "Branches" field:

*:refs/heads/*;branches/*:refs/heads/branches/* 
# instead of 
branches/*

In this case branch1 will be translated to refs/heads/branch1,
branch3 --- to refs/heads/branches/branch3.

Alternatively, if you have limited number of top-level branches, you can enumerate them explicitly:

branch1:refs/heads/branch1;
branch2:refs/heads/branch2;
branches/*:refs/heads/bra‌nches/*

edited May 23, 2017 at 10:30

CommunityBot

11 silver badge

answered Sep 9, 2013 at 7:57

VonC

1.4m569 gold badges4.8k silver badges5.7k bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Dmitry Pavlenko Over a year ago

I'll add that for your case you should enter *:refs/heads/*;branches/*:refs/heads/branches/* instead of branches/* in "Branches" field. In this case branch1 will be translated to refs/heads/branch1, branch3 --- to refs/heads/branches/branch3. Alternatively, if you have limited number of top-level branches, you can enumerate them explicitly: branch1:refs/heads/branch1;branch2:refs/heads/branch2;branches/*:refs/heads/branches/*

VonC Over a year ago

@DmitryPavlenko Good point. I have included your comment in the answer for more visibility.

kangshiyin Over a year ago

Can I get a local git repo to receive updates directly from the original svn repo by this approach, or I need to keep Atalssian as a transfer station?

VonC Over a year ago

@Eric I would recommend keeping the Atlassian tool for subsequent updates.

SKempken · Accepted Answer · 2013-09-09 07:39:23Z

0

Two options come to mind:

Clean up your SVN repo first (Move branches below /branches, where they should be according to standard layout).
Checkout using standard layout, add remote branch refs later on.

answered Sep 9, 2013 at 7:39

SKempken

4914 silver badges11 bronze badges

1 Comment

kangshiyin Over a year ago

It is not my svn repo. So I can not use method 1. Can you provide more detail on method 2, especially on the step 'adding remote branch refs'. I briefly read 'git help svn' but did not find a solution.

Collectives™ on Stack Overflow

How to clone a nonstandard svn repo to git?

2 Answers 2

4 Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

4 Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related