Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54484
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4E4092F3.2000406@garfieldtech.com>
References: <slrnj3tulc.6vi.dsp@experimentalworks.net>
	<4E3F0279.3070701@sugarcrm.com>
	<4E4092F3.2000406@garfieldtech.com>
Date: Mon, 8 Aug 2011 21:49:00 -0700
Message-ID: <CAFWS2+HY-JDDs2bGhrqYHMav7rqgGsZ7BGuT_9ACnfxk8FCg_A@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Choosing a distributed version control system for
 PHP (or not). Call for Participation.
From: ronabop@gmail.com (Ronald Chmara)

On Mon, Aug 8, 2011 at 6:52 PM, Larry Garfield <larry@garfieldtech.com> wro=
te:
> A previous poster claimed that a DVCS would lead to confusion as to what =
the
> canonical repository was. =A0That is, in my experience, a common fear of
> someone who has not used a DVCS in production.

Disclaimer: I haven't committed to PHP in years, but since my last
commit, I have worked with a lot of DVCS systems.

The whole *point* of DVCS (IMNSHO) is that the concept of "canonical
repository" is part of the *problem*, not part of the *solution*.

Here's a pretty good talk by some random guy (1:10:15 worth) on the
topic about juggling lots of code sources, and canonical
"authorities", and conflicting trees:
http://www.youtube.com/watch?v=3D4XpnKHJAok8

(Apologies if this has already been posted upthread)