Re: CVS to SVN Migration
| From: | Lukas Kahwe Smith | Date: | Fri, 25 Jul 2008 08:15:08 +0000 |
| Subject: | Re: CVS to SVN Migration | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-39303@lists.php.net to get a copy of this message | ||
On 25.07.2008, at 10:11, Rasmus Lerdorf wrote:
Lukas Kahwe Smith wrote: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. regards, Lukas Kahwe Smith mls@pooteeweet.orgWhat 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.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.