November 15, 2013
by Natalie Estrada, Marketing Events Manager
Join us on Tuesday, November 19th for the latest DevTalk Webinar: "Avoid Git Bloat and Submodule Hell".
How do you avoid the burden of working with bloated, monolithic Git repositories and sidestep the complexity of submodules?
November 14, 2013
by Bill Baffy, Software Engineer
Microsoft officially launched Visual Studio 2013 on November 13 and we are happy to be one of the Visual Studio Industry Partners to participate in the Sim-Ship of Visual Studio 2013 with our own Perforce Plugin for Visual Studio, P4VS 2013.3. This is the second Visual Studio Sim-Ship event we have participated in, having launched with the preview release of Visual Studio 2012 last year.Posted In:
November 14, 2013
by Matt Attaway, Open Source Community Manager (@p4mataway)
November 12, 2013by Matt Attaway, Open Source Community Manager (@p4mataway)
I think 'p4 edit' is by far the most cursed Perforce command on Twitter. Folks coming from Subversion and Git are accustomed to an implicit checkout workflow, and being forced to ask the version control system for permission to change something is grating. Conveniently, Perforce supports implicit checkout as well! Let's take a look.
In Perforce your normal workflow for changing a file is:
November 07, 2013by Carrie Ewing, VP of Operations
Perforce Software and our employees owe much of their success to the communities in which we live. The Perforce Software Foundation exists to share this success with the charitable organizations that make the communities what they are.
November 06, 2013by Nathan Fiedler, Software Engineer
Git Fusion’s goal is to give Git and Perforce users an uncompromised experience using the version control tool of their choice while still being able to work together seamlessly. The 2013.2 release gets us closer to that goal and, at the same time, makes Git Fusion easier to administrate and use.
Introducing Support for Git Tags
Prior to this release, any tags that were pushed to the Git Fusion service would only be preserved as long as the Git Fusion repository was intact. Now tags of commits are preserved in the Perforce depot, which allows them to be rebuilt if the need arises, as in the case of repopulating the Git Fusion repository. The commit tags can be either annotated or lightweight; both are preserved equally well.