Open pfdevmuller opened 11 years ago
OK so I hacked this into submission by changing migration.rb
to wrap all arguments to the git svn
command in quotations, and by removing the code substituting spaces with escaped spaces. I've put the patch in a gist here: https://gist.github.com/pfdevmuller/5300352
I also had to change my command line, so the repository URL was to the root of the repo, and the trunk and tags arguments went all the way down to the project folder, like so:
svn2git.bat "https://server3/svn/main" --username pmuller -v --no-minimize-url --trunk "Working Files and Tools/Namwater Reval Data Parsing/trunk" --tags "Working Files and Tools/Namwater Reval Data Parsing/tags" --nobranches
I don't think my hacks will work on Linux? If somebody wants to check, they can submit the code to be merged.
It worked better for me when I used %20 in place of the spaces in the address.
do%20not%space%20out
Confirming that using %20
works with release. Note that you have to start over by removing the .git
folder from the failed attempt before it will work.
Still struggling with this.
My repo is non standard, locally hosted and has spaces in the name (Oh the regret!)
I'm on Windows 7, 64-bit, git version
git version 1.8.1.msysgit.1
If I execute the following command in Powershell:
I get the following:
The problem is that
git svn init
creates a "Files" folder (the first term after a space in my repo URL", and the .git folder ends up inside the "Files" folder.If I run the generated git-svn command directly, in Powershell, I get the same result:
If I change the generated git-svn command to use quotes rather than the space escapes, and run that directly in Powershell, I get the desired result:
If I run the generated git-svn command directly in git bash, I get the desired result:
However, unfortunately, if I run the original svn2git command in git bash, I'm back to the original result:
It seems these issues are related to the different ways in which git-svn, svn2git, bash and Powershell (or cmd) handle spaces.
Does anybody have any suggestion, fixes or workarounds, other than installing Linux? :-)