Hi,

Integrations of Git with Perforce seem to be fashion these days, so I'd lik=
e=20
to chip in and announce another one :)

I've written a Python script called git-p4 that allows (incremental) import=
s=20
from Perforce as well as submitting changes back from git into a Perforce=20
depot.

It is currently part of the fast-export repository that Chris Lee started at

=A0=A0=A0=A0=A0=A0=A0=A0http://repo.or.cz/w/fast-export.git

I've been using it now for about a month for my everyday work (which requir=
es=20
Perforce), so it seems to work reasonably stable at least in my setup :)

The usage is pretty simple:

=A0=A0=A0=A0=A0=A0=A0=A0git-p4 clone //depot/path/my/project

Syncing:

=A0=A0=A0=A0=A0=A0=A0=A0git-p4 sync

or just

=A0=A0=A0=A0=A0=A0=A0=A0git-p4 rebase

to sync and automatically rebase into the current branch (much like git-svn=
=20
rebase :)

=A0=A0=A0=A0=A0=A0=A0=A0git-p4 submit

is used to submit changes back into Perforce (use at your own risk! :)

The import itself uses git-fast-import, so it's very fast. There is also no=
=20
need to have the imported Perforce projects in the Perforce client view as =
it=20
just uses "p4 changes //depot/path" and "p4=20
print //depot/path/file#revision", which I find very convenient and still=20
fast enough for use (since of course only changed files are printed).

It also doesn't require any additional meta-data. Instead every import comm=
it=20
has a line added to the log message that contains the Perforce path the=20
changeset comes from as well as the change number. git-p4=20
sync/rebase "parses" this on the last commit in the "p4" git branch to find=
=20
out where to continue importing for incremental imports.


What's still missing is a bit of cleanup. For example I'd like to put the=20
import branch into refs/remotes instead of refs/heads, but I've had some=20
problems with fast-import when trying that. Also the support for Perforce=20
branches isn't quite working yet. I'd ideally like to for example map a=20
structure like

//depot/project/main
//depot/project/branch1
//depot/project/branch2

into

remotes/p4/main
remotes/p4/branch1
remotes/p4/branch2

in git and still support incremental commits. But that isn't working yet ;(

Also I've never tried it on Windows and I expect problems as the script use=
s=20
pipes, calls "patch", etc.

Nevertheless I hope that this tool may be interesting for others as well.
Maybe there's a possibility of including it in git/contrib/fast-import?


Simon