问如何使用svn dcommit for svn-all-fast-export Qt脚本EN主要用于windows平台(msvc编译器)。 部署环境 ...
Runqmake && make. You get./svn-all-fast-export. (Do a checkout of the repo .git' and run qmake and make. You can only build it after having installed libsvn-dev, and naturally Qt. Running the command will give you all the options you can pass to the tool.) ...
Again, as I said, you do not run the tool on a checkout of your SVN repository. Run it on the server where the SVN repository is hosted. For example, you could call it like this: svn-all-fast-export --identity-map my-identity-map.txt --rules my-rules.txt --add-metadata /home/...
svn-all-fast-export: /build/subversion-owKwd0/subversion-1.13.0/subversion/libsvn_subr/dirent_uri.c:1011: svn_dirent_join: Assertion `svn_dirent_is_canonical(base, pool)' failed. Aborted (core dumped) but ./svn2git/svn-all-fast-export --identity-map ./account-mapping.txt --rules ./...
Seems like the application is ignoring my identity-map file. I'm using the git-svn syntax in the file, and when i run svn-all-fast-export, it seems like it either thinks I'm not passing anything to that part or ignores it completely. any ideas?
It would be cool to have a link to a documentation of the svn-all-fast-export command arguments in this repository (README). Like this one: Ubuntu Manpage: svn-all-fast-export I just noticed, that the version on the manpage is out of dat...
When running the tool without parameters, it shows --svn-branches Use the contents of SVN when creating branches, Note: SVN tags are branches as well But this does not make sense to me. The tool always uses the contents of SVN when creat...
the SVN repository is like: http://svn/Sky/trunk/folder1/ http://svn/Sky/trunk/folder2/ http://svn/Sky/branches/0.1/folder1/ http://svn/Sky/branches/0.1/folder2/ ... http://svn/Sky/branches/X.Y.Z/folder1/ http://svn/Sky/branches/X.Y.Z/folder2/ but folder2 is an svn:...
substitue branchandsubstitue repositorycan be a sed-like substitution expression likes/foo/bar/to substituebarforfooors| |_|to substitute underscores for spaces. This can e. g. be used to rename branches that have valid names in SVN but would have illegal names in Git....
docker run --rm -it -v `pwd`/workdir:/workdir -v /var/lib/svn/project1:/tmp/svn -v `pwd`/conf:/tmp/conf svn2git /usr/local/svn2git/svn-all-fast-export --identity-map /tmp/conf/project1.authors --rules /tmp/conf/project1.rules --add-metadata --svn-branches --debug-rules ...