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
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
