Perforce to subversion migration

[Nrupen Kantamneni <np...@cypress.com>]

Can we migrate the entire version history from perforce to SVN?

Thanks,
Nrupen


________________________________
This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise the sender and immediately delete this message.

Re: Perforce to subversion migration

[Nico Kadel-Garcia <nk...@gmail.com>]

On Tue, Nov 1, 2011 at 8:29 AM, Jeyanthan <je...@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.

Re: Perforce to subversion migration

[Jeyanthan <je...@collab.net>]

 > 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.

-- 
Regards,
Jeyanthan