Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:39337 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 56148 invoked from network); 25 Jul 2008 19:26:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Jul 2008 19:26:49 -0000 Authentication-Results: pb1.pair.com smtp.mail=tswicegood@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=tswicegood@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 208.113.200.5 as permitted sender) X-PHP-List-Original-Sender: tswicegood@php.net X-Host-Fingerprint: 208.113.200.5 lax-green-bigip-5.dreamhost.com Received: from [208.113.200.5] ([208.113.200.5:51834] helo=spaceymail-a3.g.dreamhost.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 56/A7-22699-8F82A884 for ; Fri, 25 Jul 2008 15:26:48 -0400 Received: from [192.168.1.101] (92.57.143.24.cm.sunflower.com [24.143.57.92]) by spaceymail-a3.g.dreamhost.com (Postfix) with ESMTP id 213C71953F9; Fri, 25 Jul 2008 12:26:45 -0700 (PDT) Message-ID: <488A2906.6000607@php.net> Date: Fri, 25 Jul 2008 14:27:02 -0500 User-Agent: Thunderbird 2.0.0.12 (X11/20080227) MIME-Version: 1.0 To: Marcus Boerger Cc: Lukas Kahwe Smith , PHP Developers Mailing List References: <40FEB6C9-9B66-4761-8B9C-0E70158D9962@wanderingknights.org> <48898544.5080100@lerdorf.com> <48898AB0.2030709@lerdorf.com> <641132640.20080725114622@marcus-boerger.de> <384297713.20080725185933@marcus-boerger.de> In-Reply-To: <384297713.20080725185933@marcus-boerger.de> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] CVS to SVN Migration From: tswicegood@php.net (Travis Swicegood) Hello Marcus; Marcus Boerger wrote: > A cvs read-only mirror would be nice to allow the old way of checking out > stuff. But there I fail to see the reason to limit our selves to one > additional other tool, nor do I see a reason to complicate matters even > more by giving people other repositories that we somehow merge or not. SVN > works everywhere and other tools can be used on top of it where ppl see > that necessary but it is not the way PHP is being developed. Or do you want > to change the whole of PHP development at the same time? > I don't presume to speak for Lukas here, nor to believe we should standardize on one particular alternative VCS (be it a DVCS or not). I think we should definitely go the SVN route as the only official way to commit to PHP with possibly a read-only mirror on CVS that could be phased out at some point in the future. That said, I think if someone is willing to step up to the plate and offer bootstrap repositories for another VCS and is willing to help support it for those who are interested in using it we would be remiss in turning them down as it's no small undertaking. According to the wiki there are over 270k commits in php-src. Using Mono (90k - 100k commits) and my own experience with smaller repositories (500 - 30k) as a guide, this means that to clone the entire history of PHP via a `git svn clone` command would take nearly a week! Using a bootstrap that is updated nightly, or even weekly, we can cut that process down to < 15 minutes. I've already volunteered on the svn-migrations list to work on an unofficial mirror as soon as the SVN import is completed. I would love to see it make its way onto a php.net server so others who are interested can benefit from the upfront work, but will be happy to host it on one of my servers like the current git clone is. -T