After seeing some heated discussions, I thought I would ask, was the possibility of just having a separate module for every major rev 3-4-5 similar to the older system discussed?
With this method cvs operations are much quicker because you are not keeping around thousands of changes in the module, most of which you may rarely look at. If for some reason you do need to view the state of main.c 4 years ago, you can always check out the corresponding major version module. I realize that the advantage of having one module for all major versions (php-src) is that it is easy to merge changes between major versions, but at some point the codebase will be completely different, so this method is really only useful if the trees are very similar, and only in the initial phases of the new major release. The merge advantage can be easily done with plain diff and patch with separate modules, and it is only a few extra steps. Also, if there are any file/directory structure changes between major versions, those can be quite the pain in the ass to administer when everything is in one big module. We all know this is one of CVS's big weaknesses. I know changing the setup to this method would be a pain, but I thought the concept should at least be considered. -Jason -- Jason Greene <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php