Hi, This was not mend as an ad or as spam. I was suggesting the use of a distributed system instead of a central VCS. I probably shouldn't have mentioned GIT specifically. Using Arch, Bazaar, Monotone or any other distributed VCS will give the same advantages.
A good article that talks about the differences between centralized and distributed revisioning systems can be found at http://www.dwheeler.com/essays/scm.html - Arnold On Mon, 2009-07-20 at 13:40 +0300, Jani Taskinen wrote: > Can I suggest you not to suggest any other VCS from now on? > If you like some VCS better, just keep that info to yourself, no need to > spam the mailing lists about it. > > --Jani > > > On 07/20/2009 01:38 PM, Arnold Daniels wrote: > > Hi, > > > > Can I suggest having a look at GIT (http://git-scm.com). It has some > > mayor advantages above SVN. The most important one is that it's a > > distributed version control system. > > > > Let's say Rasmus leads a team working on a new feature in PHP to switch > > from .ini to .yaml files for configuration. With GIT it's not needed > > that the whole team has commit access to the main GIT repository. Rasmus > > can checkout PHP to his own server. The team can checkout and commit to > > Rasmus' server. Rasmus still update the checkout of his server to get > > the changes made in the main PHP repo. When Rasmus is satisfied that the > > feature works, he (and only he) can commit it to the main repo. > > > > If you look at the linux kernel, you see that there is a whole > > hierarchy. There are lieutenants who are responsible for a certain part > > of the kernel. The lieutenant has got a small team working on that part. > > Each team member, may have a team of his own working on a specific > > feature. > > > > I would think a structure like this would work very nicely for PHP. > > > > - Arnold > > > > On Thu, 2009-07-16 at 18:09 -0500, Greg Beaver wrote: > >> Rasmus Lerdorf wrote: > >>> One of the benefits of svn is that we can do cross-branch commit pretty > >>> easily now and thus avoid multiple similar commits with annoying MFH/MFB > >>> commit log messages that are hard to track. > >>> > >>> Please don't attempt to check out all of php/php-src or pecl. I made > >>> the mistake of checking out all of pecl and it was 3.4G because you get > >>> copies of the code for every tag and branch and we have a bunch. > >>> > >>> In order to do this better, I think the best way is to use the sparse > >>> directory feature documented here: > >>> > >>> http://svnbook.red-bean.com/en/1.5/svn.advanced.sparsedirs.html > >> <snip> > >> > >> Rasmus this is brilliant. You should add this to the manual for > >> posterity in your new shiny checkout of awesomeness. > >> > >> :) > >> Greg > > > > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
