Re: Asking again... [Re: how to properly import perforce history?]

On 6/11/07, Simon Hausmann [off-list ref] wrote:

*plug* You could try with git-p4 from http://repo.or.cz/w/fast-export.git . It
should be just a matter of calling

        git-p4 clone //depot/path

Can I suggest you add a target directory mapping to your tool?
Something like:

  git-p4 clone //depot/project/path [libs/project/path] [rev-range]

The way Perforce handles branches and directories leads to
the problem that it actually cannot cleanly support neither of
them, and it is very hard to untangle a big repo which
historically has had many projects living in it.
Especially if some idiot actually tried to "do branching".

And, BTW, don't you have a small problem with filenames with
spaces and quoting?