GIT与Perforce--两个VCS将进入......一个将离开 [英] GIT vs. Perforce- Two VCS will enter... one will leave
问题描述
其中一个重大胜利是我们可以使用与网络断开的连接。另一个赢得国际海事组织是添加/结帐处理的方式。欢迎多点！此外，我们还有大约10-20个开发人员总数。
Perl 5解释器源代码目前正在经历从转换Perforce混帐。也许Sam Vilain的 git-p4raw 进口商很有意思。
无论如何，每一个集中式的VCS和大多数分布式的VCS都会变得生硬，起泡 速度 。你无法想象如何将整个项目的历史放在眼前，只需要几分之一秒的时间，直到你经历过它。即使生成包含每次提交的完整差异的整个项目历史记录的提交日志，也可以在几分之一秒内进行测量。 Git太快了，你的帽子会飞起来。 VCS必须通过网络进行传输才没有机会参与竞争，甚至不能通过千兆位以太网链接。
另外，git可以非常轻松地在选择时进行选择进行提交，从而允许工作副本（甚至在单个文件中）的更改分散在多个提交 - 如果需要的话跨不同分支。这可以让你在工作时减少精神上的注意事项 - 你不需要如此谨慎地规划你的工作，就可以决定你要做什么样的改变，并且确保推迟其他事情。你可以在你想要的时候做出任何改变，并且在需要提交的时候仍然可以解开它们 - 几乎总是很容易 - 。 存储可以在这里获得非常大的帮助。我发现一起，这些事实使我自然而然地做出比我使用git之前更多更集中的提交。这反过来不仅使你的历史通常更有用，而且对增值工具尤其有益，例如 git bisect 。
我确定有是我现在无法想象的更多事情。在git上推销团队的一个问题是，许多好处是相互关联的并且相互影响，正如我在上面所暗示的，这样很难简单地查看git的特性和好处列表，并推断它们如何将会改变你的工作流程，以及哪些改变将会是真正的改进。您需要考虑到这一点，并且您还需要明确指出。
So I'm in the process of getting GIT sold at work. First thing I need is to convince everyone that GIT is better at what they're already used to doing. We currently use Perforce. Anybody else go through a similar sale? Any good links/advice?
One of the big wins is that we can work with it disconnected from the network. Another win IMO is the way adds/checkouts are handled. More points are welcome! Also we have about 10-20 devs total.
The Perl 5 interpreter source code is currently going through the throes of converting from Perforce to git. Maybe Sam Vilain’s git-p4raw importer is of interest.
In any case, one of the major wins you’re going to have over every centralised VCS and most distributed ones also is raw, blistering speed. You can’t imagine how liberating it is to have the entire project history at hand, mere fractions of fractions of a second away, until you have experienced it. Even generating a commit log of the whole project history that includes a full diff for each commit can be measured in fractions of a second. Git is so fast your hat will fly off. VCSs that have to roundtrip over the network simply have no chance of competing, not even over a Gigabit Ethernet link.
Also, git makes it very easy to be carefully selective when making commits, thereby allowing changes in your working copy (or even within a single file) to be spread out over multiple commits – and across different branches if you need that. This allows you to make fewer mental notes while working – you don’t need to plan out your work so carefully, deciding up front what set of changes you’ll commit and making sure to postpone anything else. You can just make any changes you want as they occur to you, and still untangle them – nearly always quite easily – when it’s time to commit. The stash can be a very big help here.
I have found that together, these facts cause me to naturally make many more and much more focused commits than before I used git. This in turn not only makes your history generally more useful, but is particularly beneficial for value-add tools such as git bisect.
I’m sure there are more things I can’t think of right now. One problem with the proposition of selling your team on git is that many benefits are interrelated and play off each other, as I hinted at above, such that it is hard to simply look at a list of features and benefits of git and infer how they are going to change your workflow, and which changes are going to be bonafide improvements. You need to take this into account, and you also need to explicitly point it out.
这篇关于GIT与Perforce--两个VCS将进入......一个将离开的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
