Menu
We have a fairly large SVN repository which we are looking to migrate to perforce. We very much want to keep the ~20k revisions, the branches, etc, but in some initial tests the svn2p4 script that perforce provides wasn't able to replicate the full structure.
Have people had success with this tool, or were there others that my google searching didn't turn up? Best practices and tips are welcome.
356
SVN is better than Git for architecture performance, binary files, and usability. And it may be better for access control and auditability, based on your needs.
Git has the advantage that it's MUCH better suited if some developers are not always connected to the master repository. Also, it's much faster than SVN. And from what I hear, branching and merging support is a lot better (which is to be expected, as these are the core reasons it was written).
SVN is a popular tool for code hosting. It is used to manage different versions of files like source code, documentation and more. It keeps history and project data. Subversion is an open-source tool and comes under the Apache License.
The difference between Git and SVN version control systems is that Git is a distributed version control system, whereas SVN is a centralized version control system. Git uses multiple repositories including a centralized repository and server, as well as some local repositories.
Vitalii Pokrovskii and Mark Fridrich created svn2p4, a perl script that will 'sync and replay' to import every change set into perforce.
You can find it on the perforce wiki. They also gave a presentation about it at the 2007 Perforce User's Conference.
update 2012: Another solution is to use p4convert-svn. Details here: p4convert-svn at perforce site
113
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
