Even with DVCS, the convention is to designate one of the repositories
as the "master" so everyone can pull/push (checkin/checkout) their
changes that end up in a tagged release.  The change in mindset has
more to do with "file versions" in CVS and Subversion versus "change
sets" in dvcs.


> The thing to bear in mind is that if you're used to a conventional VCS with
> a master repository, a DVCS requires a major change to your mindset to use
> it in the way it is meant to be used. You can still use it the old-fashioned
> way, but you won't be using the power it is capable of.
U2-Users mailing list

Reply via email to