A little, badly written tool to keep a Mercurial repository in
sync with a Perforce one
Eric M. Hopper
hopper at omnifarious.org
Tue Sep 27 01:32:17 CDT 2005
Someone asked me to post this...
This tool is ad-hoc and not terribly well written. It assumes that it
will be run out of the base directory of a Perforce repository that is
also a Mercurial one. It runs the p4 command-line client, so you'd
better have a .p4config file or all the funny environment variables set.
Lastly, it assumes that the Perforce repository represents a single
directory in the Perforce depot.
With some programming, those limitations could probably be lifted. But
I wrote this for me, and I didn't need those capabilities. :-)
I also added a link to the ConvertingRepositories wiki page.
Have fun (if at all possible),
The best we can hope for concerning the people at large is that they
be properly armed. -- Alexander Hamilton
-- Eric Hopper (hopper at omnifarious.org http://www.omnifarious.org/~hopper) --
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 185 bytes
Desc: This is a digitally signed message part
Url : http://www.selenic.com/pipermail/mercurial/attachments/20050926/ffaa7302/attachment.pgp
More information about the Mercurial