Re: [PHP-DEV] DOM/XML in 4.0.7

2001-06-29 Thread Andi Gutmans
At 02:30 PM 6/27/2001 -0400, Colin Viebrock wrote: For 4.0.6 I rolled back the DOM/XML changes. It seems as if the current upgrade isn't being fixed. Maybe we should revert it back to what it was in 4.0.6 until it gets a thorough make over? You love to make me work, huh? :) Seriously, if

Re: [PHP-DEV] DOM/XML in 4.0.7

2001-06-28 Thread Colin Viebrock
For 4.0.6 I rolled back the DOM/XML changes. It seems as if the current upgrade isn't being fixed. Maybe we should revert it back to what it was in 4.0.6 until it gets a thorough make over? You love to make me work, huh? :) Seriously, if we stick with the 4.0.6 version, that's fine.

[PHP-DEV] DOM/XML in 4.0.7

2001-06-27 Thread Andi Gutmans
Hey, For 4.0.6 I rolled back the DOM/XML changes. It seems as if the current upgrade isn't being fixed. Maybe we should revert it back to what it was in 4.0.6 until it gets a thorough make over? Andi -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL

Re: [PHP-DEV] DOM/XML in 4.0.7

2001-06-27 Thread Christian Stocker
In article [EMAIL PROTECTED], Andi Gutmans [EMAIL PROTECTED] wrote: Hey, For 4.0.6 I rolled back the DOM/XML changes. It seems as if the current upgrade isn't being fixed. Maybe we should revert it back to what it was in 4.0.6 until it gets a thorough make over? yes, please :=) chregu,

Re: [PHP-DEV] DOM/XML in 4.0.7

2001-06-27 Thread Andrei Zmievski
On Wed, 27 Jun 2001, Andi Gutmans wrote: Hey, For 4.0.6 I rolled back the DOM/XML changes. It seems as if the current upgrade isn't being fixed. Maybe we should revert it back to what it was in 4.0.6 until it gets a thorough make over? Might not be a bad idea. The upgrade Ulf put in

Re: [PHP-DEV] DOM/XML in 4.0.7

2001-06-27 Thread Andi Gutmans
At 09:00 AM 6/27/2001 +0200, Christian Stocker wrote: In article [EMAIL PROTECTED], Andi Gutmans [EMAIL PROTECTED] wrote: Hey, For 4.0.6 I rolled back the DOM/XML changes. It seems as if the current upgrade isn't being fixed. Maybe we should revert it back to what it was in 4.0.6 until