一个词概括Git和其他DVCS [英] One word to summarize Git and other DVCS

问题描述

当我熟悉Git时，我越来越感到:

As I getting acquainted with Git, I feel more and more that:

Git和其他DVCS比传统的集中式VCS更进一步，因为它们不仅检出有问题的文件，而且还检出有问题的文件. 完整版本数据库.

Git and other DVCS jump a step futher than traditional centralized VCS in that they not only check out files in question, but also the whole version database.

我认为这是DVCS和CVCS之间的主要区别，也是DVCS所有其他优点的主要立足点.

I think this is the major difference between DVCS and CVCS, and also the major foothold of all other benefits of DVCS.

或者，让我们这样说:

多个本地VCS +集中备份= DVCS.

Multiple Local VCS + A Centralized Backup = DVCS.

将以上等式更改为:

多个本地克隆+集中备份= DVCS.

Multiple Local Clones + A Centralized Backup = DVCS.

对吗?

推荐答案

您所描述的是分布式系统的本质:克隆了整个存储库(具有完整的历史记录).

What you are describing is the very nature of a distributed system: the whole repository is cloned (with its full history).

DVCS将版本控制(分支和标签)与发布(从远程回购推入/拉出)混合在一起

a DVCS mixes version control (branching and labels) with publication (push/pull to/from remote repo)

但是还有其他特征区分DVCS和CVCS.
尤其是在工作流程术语中.请参阅"描述使用版本控制的工作流程(VCS或DVCS)"

But there are other characteristics that differentiate a DVCS from CVCS.
Especially in terms of workflow. See "Describe your workflow of using version control (VCS or DVCS)"

也不要忘记 Redmine项目管理系统

And don't forget that a DVCS doesn't have authorization or authentication. However, there are solutions to provide those, e.g. apache2-authn-redmine in combination with the Redmine Project Management System

OP smwikipedia 添加:

多个本地VCS +集中备份= DVCS.

Multiple Local VCS + A Centralized Backup = DVCS.

我认为您无法以这种方式进行总结，尤其是考虑到由于大多数VCS(SVN，ClearCase，Perforce等)都没有本地"存储库，因此很难模拟推/拉功能，只能是本地工作空间，并且在很大程度上取决于其中央存储库.

I don't think you can summarize that way, especially considering it would be difficult to emulate the push/pull features since most of the VCS (SVN, ClearCase, Perforce, ...) have no "local" repo, only local working spaces, and depend heavily on their central repo.

这篇关于一个词概括Git和其他DVCS的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！