Re: Choosing a distributed version control system for PHP - problems

From: Date: Thu, 18 Aug 2011 10:22:03 +0000
Subject: Re: Choosing a distributed version control system for PHP - problems
References: 1 2 3 4 5 6 7 8  Groups: php.internals 
Request: Send a blank email to internals+get-54676@lists.php.net to get a copy of this message
On Thu, Aug 18, 2011 at 11:49 AM, Lester Caine <lester@lsces.co.uk> wrote: > This was the problem I hit last year. A nice CVS repo got translated into > some 200 git repo's, but there still is no easy way of building a 'project' > that pulls the say a core build with all the essential modules. You end up > writing scripts to pull each and manage them individually. I would > anticipate that php is probably larger than the libraoffice codebase, so > being able to properly manage modular builds is going to be important? Again, it is totally unrelated to git or hg but the choices of the developers. The discussion about having extensions (or whatever else) in external modules or in core (no matter which system is used, svn, git or hg) is not related to this topic. ps: it's libreoffice. Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org

« previous php.internals (#54676) next »