Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:39353 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 20907 invoked from network); 26 Jul 2008 13:59:19 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Jul 2008 13:59:19 -0000 X-Host-Fingerprint: 84.60.123.80 dslb-084-060-123-080.pools.arcor-ip.net Received: from [84.60.123.80] ([84.60.123.80:9015] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 35/B2-04212-4BD2B884 for ; Sat, 26 Jul 2008 09:59:18 -0400 Message-ID: <35.B2.04212.4BD2B884@pb1.pair.com> To: internals@lists.php.net Date: Sat, 26 Jul 2008 15:59:13 +0200 User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707) MIME-Version: 1.0 References: <40FEB6C9-9B66-4761-8B9C-0E70158D9962@wanderingknights.org> <48898544.5080100@lerdorf.com> <48898AB0.2030709@lerdorf.com> In-Reply-To: <48898AB0.2030709@lerdorf.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 84.60.123.80 Subject: Re: [PHP-DEV] CVS to SVN Migration From: sebastian.deutsch@9elements.com (Sebastian Deutsch) Rasmus Lerdorf schrieb: > Lukas Kahwe Smith wrote: >>> The git and hg integration with svn is also good so any developer who >>> prefers to have a local repository can very easily use either git or >>> hg and easily merge into the central svn repository. >> >> >> However I think we should provide the infrastructure for developers to >> setup a dvcs. I dont know if we want to standardize on a specific one. >> But collaboration on exterimental stuff that requires a dvcs should be >> possible on php.net servers. > > What do you mean by that? hgsvn and git-svn don't need any server-side > support to enable you to work locally and do local git or hg checkins > and then sync to the central svn repository when you are ready. > > -Rasmus It should not be a question of product, but of workflow. An example: A lot of time is needed when porting bugfixes from a stable branch to the development branch and vice versa. In my experience a DVCS reduces this time immense. PHP-SRC consists of a lot of branches (and tags) and the goal should be to port code as easy as possible between different branches. Using a DVCS which is based on a direct acyclic graph (short DAG) can change the way you work with a VCS. Probably most of you who have worked with a DVCS know the technique of DaggyFixing (http://www.venge.net/mtn-wiki/DaggyFixes). Basically it means that a Bugfix is not committed to the revision where it is fixed, instead the Bugfix Graph is inserted right after the feature where the problem occurred and then the merge is propagated to the head revision. If you take SVN and export it locally to a DVCS, then do some coding and reimport your patches, this advantages are probably lost (though I have to admit that I never tried it). Sebastian