[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Perforce to subversion migration

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Tue, 1 Nov 2011 08:44:47 -0400

On Tue, Nov 1, 2011 at 8:29 AM, Jeyanthan <jeyanthan_at_collab.net> wrote:
>> Can we migrate the entire version history from perforce to SVN?
> Hi Nrupen,
> Visit http://p42svn.tigris.org/ to perform the migration.
> p42svn is a Perl script to migrate revision history from a Perforce depot to
> a Subversion repository.

Be careful not to sprain yourself in the process, though, and review
the changes in authentication and access control you'll want to
negotiate before the move.

In general, I've found source control migrations to be an excellent
opportunity to do a clean export and create a locked, read-only
repository for the old materal. I also tend to *break* the history at
migration time, and create a new, stripped down repositor with
consistent setting of features like svn:ignore, svn:keywords,
svn:executable, svn:mimetypes, or svn:externals. It can really help
avoid confusion about the debris that tends to accumulate in an old
source control system.
Received on 2011-11-01 13:45:22 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.