Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:39309
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 85.214.94.56 as permitted sender)
Date: Fri, 25 Jul 2008 11:46:22 +0200
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <641132640.20080725114622@marcus-boerger.de>
To: Lukas Kahwe Smith <mls@pooteeweet.org>
CC: PHP Developers Mailing List <internals@lists.php.net>
In-Reply-To: <FE5F57F4-0861-4CAB-A6E8-5F4DC711BE59@pooteeweet.org>
References: <40FEB6C9-9B66-4761-8B9C-0E70158D9962@wanderingknights.org> <d4ad84b50807250033r36f92879r74d0679026626f04@mail.gmail.com> <48898544.5080100@lerdorf.com> <A1337AF2-50A0-415E-B796-259AFC1B51AD@pooteeweet.org> <48898AB0.2030709@lerdorf.com> <FE5F57F4-0861-4CAB-A6E8-5F4DC711BE59@pooteeweet.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] CVS to SVN Migration
From: helly@php.net (Marcus Boerger)

Hello Lukas,

Friday, July 25, 2008, 10:15:08 AM, you wrote:


> On 25.07.2008, at 10:11, Rasmus Lerdorf wrote:

>> 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.

> I mean that if several people work on a changeset, that they still  
> might want to have a join central repo. Of course dvcs allows direct  
> exchange of patches as well, but it might still be a good idea to have  
> this central dvcs repo for historical reasons (lets say some stuff is  
> attempted, it is then abandonded and then picked up by someone else).

> Also in terms of standardization I mean that even core developers can  
> get overwhelmed if they end up having to use git here, and hg there.  
> Then again we are still far away from having that many different  
> subprojects that need dvcs.

I still cannot follow you. Do you even know about these tools?

If two parties use git or hg they are all fine. And everyone else is fine
too because they don' t have to learn dcms (btw, it's a distributed cms
as in code/configuraqtion management system:
http://en.wikipedia.org/wiki/Code_management_system). Anyway you don't want
to teach for example our documentation group to use git or hg. Besides the
fact thaqt there is no windows support for git they do not have the
slightest use whatsoever for local branching. Though of course anyone who
is can safely start it's own perfectly working local one.

marcus




Best regards,
 Marcus