Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54649
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4E4BD968.6060706@garfieldtech.com>
References: <4E4B7845.8@lsces.co.uk>
	<4E4BD968.6060706@garfieldtech.com>
Date: Wed, 17 Aug 2011 17:15:05 +0200
Message-ID: <CAEZPtU4cmz2M2OUsgRq=tMUhyge7+0wzbe9hMpoi-RS3SEKXwA@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] Choosing a distributed version control system for PHP - problems
From: pierre.php@gmail.com (Pierre Joye)

On Wed, Aug 17, 2011 at 5:08 PM, Larry Garfield <larry@garfieldtech.com> wr=
ote:
> I'd be happy to put people in touch with members of the team that handled
> the Drupal git migration earlier this year. =A0They successfully migrated=
 > 1
> million lines of code with a 10 year history across a few thousand
> repositories from CVS to Git without a hitch (at least no hitch that the
> outside world saw). =A0That sort of practical experience should be helpfu=
l in
> determining some of the finer points of how you'd actually DO that for a
> project like PHP.

Another great example of a successful is the freedesktop project. They
have 100s of sub project and each of them have modules.

However, I fear that Lester is mixing topics in all possible ways and
that's slightly confusing for outsiders.

Cheers,
--=20
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org