I have checked out php5 and used HEAD. -> Looks good
On my harddisk is also a checkout of php4 with tag PHP4_3 (this seems to be the same with the STABLE snapshot)
Today I checked also out php4 HEAD and have seen that this seems to look similar to PHP4_3 only the fileversions were updated by imajes.
So what I want to know:
How should I commit changes to PHP 4.3.3RC2 (using PHP4_3 as TAG or with the new php4-HEAD checkout)? If the last is correct (HEAD) somebody should set the TAG HEAD==PHP4_3 - this would make life easier for all...
Some clearance would be nice! Uwe
At 14:21 23.06.2003 +0100, James Cox wrote:
> > The point is that there are now a number of core developers > who updated their existing php5 checkouts and now have a load > of crap from 4.3 merged into their php5 development. >
For what it's worth, the last 5 or so warning emails I have dropped onto the list making it very clear what the path to upgrade would be should have made it very clear as to what was going to happen.
That said, I did not take into account developers who would, for their own reasons, update cvs as the first thing they'd do before reading mail. (I always read mail first, so perhaps you can excuse me that assumption). At any rate, it should still be possible to do a cvs diff into a patch for new trees, and with a bit of magic you could diff against $current_revision - 1.
But, before you lump scorn and disdain all over me, can I just point out that, even though I made the mistake of not giving you guys some time to migrate, this "hackish, not thinking things through" method of doing things got us into this problem in the first place. However much it tries to be able to do it, cvs is just not capable of the revision management that is needed unless you truly are a RCS expert, hence the need for an entirely separate module.
By pushing php4 HEAD back to development (and to be honest, I'm not sure if it's ever going to get back to being a usable codebase, it's so broken with various cvs deletes etc that need to get readded) it forces people to stop using it to check in php5 stuff. Of course, I could have alternatively denied access to that tree for a couple of days whilst you got reaquainted -- but then again, that would have slowed 4.3.3.
So apologies for the slight inconvenience... But lets be honest, if it will take you longer than 1/2 hour to get your trees in order again, then you aren't using revision control properly.
-- james
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
----- Uwe Schindler Addr 1: Bamberger Str. 24a, D-96049 Bamberg Addr 2: Drausnickstr. 153, D-91052 Erlangen http://www.thetaphi.de - http:///www.schindlers-software.de eMails: [EMAIL PROTECTED] (private); [EMAIL PROTECTED] (company) Tel./Fax: +49 700 PCLATEIN (+49 700 72528346)
Schindlers Software - Home of Schindlers PC-LATEIN 3.10
DIE Software zum Lateinlernen!
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
