Cloning / Converting Perforce Local Workspace to Mercurial Repo

I'm new to Perforce and Mercurial, so bear with me. I would like to use Mercurial to interact with Perforce as follows:

I am browsing the local Perforce workspace using the P4V client. Then I clone the Mercurial repo of this workspace and use this cloned repo for all of my work. When I need updated files, I would first update the local Perforce workspace and then pull the Mercurial repo out of this. When I’m ready to make a deal, I push my changes to the Perforce local workspace. Then I use the P4V client to make changes to the Perforce workspace in the Perforce repository. Essentially, the Perforce local workspace is a proxy relay for Perforce.

The reason for this setting (compared to the usual scenario of direct pulling and switching to Perforce-repot) is that I need to perform some configuration through the P4V client (for example, displaying / renaming files and directories).

I looked at the conversion and performance extensions, but I'm not entirely sure that they do what I want. They seem to do a one-time conversion, and then after that talk directly to Perforce's reputation. Any help would be appreciated.

+3
source share
2 answers

The conversion performs incremental conversion, where it will only convert new changes, but only unidirectional (perforce → mercurial).

, , - .

, Subversion Mercurial wiki Mercurial /atop Subversion , . , , , .

0

Perfarce , . , Perforce .

, , SO, , , .

Perfarce, - .

0

All Articles