问题描述
我刚刚换了工作.我以前的雇主使用 Subversion，我的新雇主使用 Perforce.
I've just changed jobs. My previous employer uses Subversion, my new employer uses Perforce.
作为用户，是否有任何资源可以帮助我将我的心智模型从 Subversion 更改为 Perforce 模型?常见的 SVN 命令的类比是什么?哪些概念的实现方式不同?
Are there any resources out there that'll help me, as a user, change my mental model from a Subversion one to a Perforce one? What are the analogs to common SVN commands? Which concepts are implemented differently?
我对 Perforce 与 Subversion 的优缺点并不特别感兴趣 - 已经做出了决定.关于 S.O. 还有很多其他问题.覆盖那个.我想知道我必须(或不)进行哪些心理调整.
I'm not particularly interested in the pros and cons of Perforce vs Subversion - the decision's been made. There are plenty of other questions on S.O. covering that. I'd like to know what mental readjustment I'll have to make (or not).
推荐答案
Perforce 和 Subversion 非常相似，它们都具有文件组的原子提交和基于路径的分支.
Perforce and Subversion are quite similar, they both feature atomic commit of groups of files, and path-based branching.
Perforce 具有:
Perforce has:
a) 待定变更集 - 您可以将正在编辑的文件分组并操作这些组.
a) Pending changesets - you can group files that you are editing into groups and manipulate the groups.
b) Client-Specs - 您可以以相当复杂的方案将存储库映射到您的本地工作空间.
b) Client-Specs - you can map the repository to your local work-space in quite complicated schemes.
c) 无外部 - 因此您不能将存储库的同一部分映射到工作空间中的多个位置，或将其他存储库映射到工作空间中的子目录.
c) No external - so you can't map the same part of the repository to multiple locations in your work-space, or map other repositories to sub-dirs in your work-space.
d) 合并跟踪，这是 Subversion 的一项新功能.
d) Merge-tracking, which is a new feature for Subversion.
e) 强大的服务器连接:您必须在编辑文件之前告诉服务器，服务器使用此信息来很好地了解您的本地工作空间状态，从而加快更新速度.
e) Strong server connections: You have to tell the server before editing a file, and the server uses this information to keep a good idea of your local work-space state, which makes updates faster.
这篇关于Perforce 对于 Subversion 用户?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！