gpt4 book ai didi

version-control - 集中式和分布式版本控制系统的比较

转载 作者:行者123 更新时间:2023-12-03 05:15:04 27 4
gpt4 key购买 nike

使用集中式版本控制系统与分布式版本控制系统 (DVCS) 的优点和缺点有哪些?您在 DVCS 中遇到过任何问题吗?您是如何防范这些问题的? 让讨论工具保持不可知论,并将激烈的争论降到最低。

对于那些想知道有哪些 DVCS 工具可用的人,以下是最著名的免费/开源 DVCS 的列表:

最佳答案

来自my answer到另一个question :

Distributed version control systems (DVCSs) solve different problems than Centralized VCSs. Comparing them is like comparing hammers and screwdrivers.

Centralized VCS systems are designed with the intent that there is One True Source that is Blessed, and therefore Good. All developers work (checkout) from that source, and then add (commit) their changes, which then become similarly Blessed. The only real difference between CVS, Subversion, ClearCase, Perforce, VisualSourceSafe and all the other CVCSes is in the workflow, performance, and integration that each product offers.

Distributed VCS systems are designed with the intent that one repository is as good as any other, and that merges from one repository to another are just another form of communication. Any semantic value as to which repository should be trusted is imposed from the outside by process, not by the software itself.

The real choice between using one type or the other is organizational -- if your project or organization wants centralized control, then a DVCS is a non-starter. If your developers are expected to work all over the country/world, without secure broadband connections to a central repository, then DVCS is probably your salvation. If you need both, you're fsck'd.

关于version-control - 集中式和分布式版本控制系统的比较,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/111031/

27 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com