Perforce is a Git Developer. We’ve been studying Git for some time. We like to keep an eye on players and technology in our space, partly because it’s something we think our customers appreciate, partly because it’s due diligence as a leader in the SCM/Version Management space, and partly because it’s just plain interesting! But something unexpected happened last summer as a result of this study of competing technologies: the relationship between Git and Perforce turns out to have synergistic appeal with a peanut butter twist, as outlined in my blog articles Perforce and DVCS: Two great tastes that taste great together and Git as a Perforce Client.
But if you want to use Git and Perforce together today, you’ll likely be looking at the git-p4 feature of Git as either a tool or a starting point. So to get you a little further along the road, we’ll be making an increased effort on git-p4 in the coming months. Here’s where you can give us a hand: letting us know what’s important to you in a git-p4 feature set. Please add your suggestions to the comments below! [p4 blog]
I just started trying out git-p4 yesterday for a very small internal tool, so this is really good news. As a CM Engineer, I pretty much live in Perforce, but it’s a bit awkward for working on small internal tools where I might want to have several experimental branches. I’m quite new to git, but I’ve already found that its capability for that sort of work more than lives up to the hype.