November 25, 2014
Murtaza Amiji, Senior Director of Product Management
Here's what's new from Perforce in November.Posted In:
November 24, 2014by John Williston, Product Marketing Manager at Perforce Software
This is part 3 of a 6-part series on Git commands.
One of Git’s particularly useful features is stashing. The Git newbie can be overwhelmed easily with the power of light, in-place branching, particularly if his colleagues are Git experts who branch all the time.Posted In:
November 21, 2014by Liz Lam, QA Lead Engineer (@p4liz)
This is part of a blog series designed to explore the stories of our Women in Tech at Perforce. It's been fun and inspiring talking to each one of these women. As they share where they've been and how they came to where they are now, it is my hope that others will be encouraged and inspired too.
Steph Turner is no stranger to the Perforce Community. A seasoned developer with a wealth of knowledge, she is also very involved in creating opportunities for girls in technology and youth sports. She is currently working with the public schools, Boys and Girls Club, the Perforce Foundation and private industry to develop a hands on technology program that exposes high school and college students to current industry skills and practices. Steph also started two tournament girls basketball programs and sits on the Board for Alameda Youth Basketball.Posted In:
November 21, 2014by John Williston, Product Marketing Manager at Perforce Software
This is part 2 of a 6-part series on Git commands.
Some of the Git command syntax can be described (charitably) as baroque, and it’s unsurprisingly one of the roadblocks that can slow down newbies. Thankfully, Git provides an under-utilized facility to address this known as aliases. A Git alias is not dissimilar from a Bash (or other shell) alias, in that it defines a piece of text as a key that Git will recognize and expand into something else, optionally including arguments in the process.Posted In:
November 19, 2014
by Frank Compagner, Lead Tools Programmer at Guerrilla Games
This year marks the 10 year anniversary of Guerrilla Games moving all code and assets into Perforce. Back then, a project was done by 35 developers and it had about 200 GB of data in the depot. 10 years on, our last project was produced by 350 people and has a head revision that’s just shy of 2 TB. We’ve learned a lot along the way in terms of dealing with the increase in data and team sizes, as well as general complexity.
November 18, 2014by John Williston, Product Marketing Manager at Perforce Software
As a relatively new Perforce employee, I’m still in the process of migrating all my old code from other tools. So this is part one of a little blog series covering the various tools in the chain I’ll be using to ultimately get all of my code into the Perforce Versioning Engine.
Recently, I needed code from projects still in Subversion, and integrating them with the rest of my code (the majority of which is in Mercurial) seemed like a good first step. It also provided an opportunity to evaluate how well Mercurial handles imports from Subversion.Posted In: