4 ms·
You also need tools that support the workflow. I love small self-explanatory commits. In git, it's easy to do. Recently I switched to a Perforce organization an
by StilesCrisis 1y ago
You also need tools that support the workflow. I love small self-explanatory commits. In git, it's easy to do. Recently I switched to a Perforce organization and it's a disaster. P4 doesn't support stacked CLs and it dramatically hurts engineering quality. Everyone lands mega-CLs because it's the only supported workflow.
- epage 1y agoSorry to hear about the use of Perforce. Even the dinosaur of a company I used to work at shifted away. (granted, I know VCS like it are still good for assets)
- skirmish 1y agoHave you tried using the git adapter to Perforce backend [1]? It should let you avoid mega-CLs. When Google used to use Perforce, an internal somewhat similar but a bit more advanced tool git5 was very popular. [1] https://git-scm.com/docs/git-p4 https://git-scm.com/docs/git-p4
- StilesCrisis 1y agoThe adapter breaks down on sufficiently massive repos. Unfortunately, there's a reason Perforce is still in use despite no one liking it. Git scales via sub-repos, but those have their own drawbacks, and no one is enthusiastic enough about this to champion it.
- haradion 1y agoWith the right workspace mapping, you can pull in just part of the depot, which makes the repo size a lot more manageable.