How can we migrate the folders with space in their name?

Hi,

We are trying to migrate different subfolders from a parent SVN repo as different repositories on GIT . Some of these folders have space in their names and code is not getting migrated in this case.
Parent SVN Repo path: /MCCBPM (Attached is the screenshot - SVNParentRepo)
The path https://svn.dts.fm.rbsgrp.net/MCCBPM/TMGRS/60%20Day%20Expiry/Trunk needs to be the master
and https://svn.dts.fm.rbsgrp.net/MCCBPM/TMGRS/60%20Day%20Expiry/Branches/ should have the branches

Below is the mappings that we have tried-
SVN URL was set to https://svn.dts.fm.rbsgrp.net/MCCBPM

Mapping-
trunk = TMGRS/60%20Day%20Expiry/Trunk:refs/heads/master
branches = TMGRS/60%20Day%20Expiry/Branches/:refs/heads/

However, even if the tool shows the migration completed, the repository is till empty.
Please let us know how we can proceed in this case?

Thanks

MCCBPM-Subfolder_SVN

Adding screenshots of bitbucket repository as well.

Hello,

it’s not needed to use URL encoding in the branches names, set them with the spaces as they are in SVN:

 trunk = TMGRS/60 Day Expiry/Trunk:refs/heads/master
 branches = TMGRS/60 Day Expiry/Branches/*:refs/heads/*

Note, that spaces in branches names will be replaced with “+” sign after translation. That is, if a branch in SVN has the name “new branch”, then with this mapping it will appear in Git under name “new+branch”.

Thank you for the information.
Is there any way we can avoid having + in branch name for the existing branches?

Git does not support space in references names, that’s there reason why spaces are being replaced with “+” sign. I’m afraid there’s no way to get branches in Git with the same names with spaces as in SVN.

Thank you for the update.
Also, can you please let us know if the file permissions are also carried over when we migrate it from SVN to GIt using SVN mirror?
For example- We have a repo on SVN Repo1, it has some unix shell scripts which are default created in executable mode when we did an svn checkout. We migrated it to GIT using SVN mirror under Repo2 on Bitbucket. When we did a git clone from the migrated repo, those files are created with no exec permission.

Thanks

Hello,

no, files permissions are not being persisted through the import, files are being created with permissions set that are configured on the receiving SubGit server.

Hi,

By SubGit server, do you mean the server where the SVN mirror is hosted and the repos are migrated or do you mean the GIT client using which we will clone the migrated repository?

Thanks

Hi,

I meant Git client, actually.