Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>What you are describing is the very nature of a distributed system: the whole repository is cloned (with its full history).</p> <blockquote> <p>a DVCS mixes version control (branching and labels) with publication (push/pull to/from remote repo)</p> </blockquote> <p>But there are <a href="https://stackoverflow.com/questions/995636/popularity-of-git-mercurial-bazaar-vs-which-to-recommend/995799#995799">other characteristics</a> that differentiate a DVCS from CVCS.<br> Especially in <a href="https://stackoverflow.com/questions/2563836/sell-me-distributed-revision-control/2563917#2563917">terms of workflow</a>. See "<a href="https://stackoverflow.com/questions/2704996/describe-your-workflow-of-using-version-control-vcs-or-dvcs">Describe your workflow of using version control (VCS or DVCS)</a>"</p> <p>And don't forget that a <a href="https://stackoverflow.com/questions/5683253/distributed-version-control-systems-and-the-enterprise-a-good-mix/5685757#5685757">DVCS doesn't have authorization or authentication</a>. However, there are solutions to provide those, e.g. apache2-authn-redmine in combination with the <a href="http://www.redmine.org" rel="nofollow noreferrer">Redmine Project Management System</a></p> <p>The <a href="https://stackoverflow.com/users/264052/smwikipedia">OP smwikipedia</a> adds:</p> <blockquote> <p>Multiple Local VCS + A Centralized Backup = DVCS.</p> </blockquote> <p>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.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload