Re: [p4] Making Helix depots accessible with Git clients

Posted on behalf of forum user 'Matt Janulewicz'.

The way I look at it, GitFusion uses Perforce as a base, therefore your git
users are the exception and have to make concessions to work with the base code.

Helix4Git reverses that relationship by making git data objects first class
citizens, so then your 'native' p4 users have to make concessions
(training, terminology, etc.) to work with those repos.

I would say that after having a few year's experience supporting GitFusion,
it is for the most part transparent to git users. They mostly don't notice
that Perforce is the back-end, until something goes wrong and it spits out a
non-git error message that looks foreign to them.  :)

But as mentioned, GitFusion is on the way out, if it isn't unsupported
already. I don't see any clear announcement about development stopping on
GitFusion, just, as you've also noticed, it's not downlodable from the
main Perforce page, and is barely mentioned anywhere. It still looks to be
available on the ftp site as well as in the RHEL/CentOS Perforce yum repo.

It might also be worth noting that Helix4Git is an extra license (cost) on top
of Perforce licenses, so there are pluses and minuses to both GitFusion and
Helix4Git, for sure.

Newer versions of git have a p4 interface built in and it's fairly usable
for cloning a branch at a time and pushing changes. Maybe a little awkward, but
git users are used to awkward things so it shouldn't be too much of a
stretch. Ha ha. I kid.



--
Please click here to see the post in its original format:
  http://forums.perforce.com/index.php?/topic/5688-making-helix-depots-accessible-with-git-clients
_______________________________________________
perforce-user mailing list  -  [email protected]
http://maillist.perforce.com/mailman/listinfo/perforce-user