Category: General Geekery
October 10, 2013by Sam Stafford, Developer at Perforce Software
In the days before streams, it was commonly accepted that if files had different names in different branches, you would need to set up a branch spec that mapped one set of file names to the other if you wanted to integrate changes between those branches. When we began developing streams functionality, we knew we would need to provide another way to handle refactoring within streams, since the branch view used to merge changes between a stream and its parent is dynamically generated and is supposed to be a relatively simple function of the paths specified for each stream – hence we came up with a system for matching different filename variants within a source and target to each other and setting up resolves between them.
September 16, 2013by Allan Yu, User Experience Designer
As a Perforce user, you have a voice that can shape the future of our products. And we are listening closely. Collecting feedback from our customers to understand their wants and needs is always an important step when defining product roadmaps and prioritizing upcoming features.
September 03, 2013
by Liz Lam (@p4liz)
For the past several months, I've been on loan to the Git Fusion QA team. It's been interesting to see the intersection of these two very different systems. One thing our development team has done is extended some of the git commands to return Perforce and Git Fusion specific information. Here's a page from our user manual:Posted In:
August 26, 2013by Sam Stafford, Developer at Perforce Software
Sharp-eyed users may have noticed the addition of a new undoc option to the command line client in 2013.2:
August 22, 2013by Jennifer Bottom, Support Engineer at PerforcePosted In:
May 31, 2013by Matt Attaway, Open Source Community Manager (@p4mataway)