2

We are looking at moving away from Perforce (mostly due to the pain of having to always be connected to its sever and the lack of support for moving bug fixes between branches, and also wish to introduce a tool for code reviews)

However we still need all the history that is in Perforce, so is there a way to move to Kiln while keeping the history.

(Someone else in the company has tried importing from Perforce into Mercurial but could not find a good way of keeping the history. As I understand it Kiln is a hosted service that provides Mercurial plus a code review tool.)

Ian Ringrose
  • 51,220
  • 55
  • 213
  • 317
  • There is a conversion utility that's part of Mercurial that preserves at least some of the history that converts from Perforce. But I don't know anything about Proforce. Do you mean Perforce? I also wrote my own history preserving conversion utility for Perforce long ago, but it's been supplanted by the one built into Mercurial. – Omnifarious Oct 29 '10 at 08:20
  • 2
    Why do you say that Perforce lacks support for moving fixes between branches? Cherrypicking works perfectly fine with P4. As far as code reviews e.g. Crucible supports Perforce. Also, the 2010.1 release of P4V supports moving workspaces offline (admittedly a bit clunky though). – rjnilsson Nov 01 '10 at 07:58

1 Answers1

2

First look here:

Mercurial Wiki entry for converting from Perforce

Since the conversion of VC systems with different paradigms is non trivial, you might want to tweak one of the methods considered there.

If this fails totally, you can also try to convert to a intermediate VC system like, SVN, CVS, git and then to mercurial.

Once you got it in mercurial locally you can always move it up to Kiln or one of the other hosted systems.

Peer Stritzinger
  • 8,232
  • 2
  • 30
  • 43