Re: [PHP-DEV] Moving output.c from ext/standard to main/
Zeev Suraski wrote: It's been bugging me for over a year now, and I'm now trying to figure out the best way to do it. output.c sits today in ext/standard, which is wrong, as it's really a part of the inner core of PHP, and not a set of functions. If I move the file in the CVS repository and fix the references, then everything would be fine, history would be retained, except checking out old CVS's will no longer work. If import the file into main/ and delete it from ext/standard, we lose the history for it, which is sucky. I'm thinking about moving the file in CVS, and in addition to fixing the HEAD branch, fix also the 4.0.6 branch, so that we at least can check out one version back. What do you guys think? If you mv the file on the server you'll break checkouts of older code, won't you? What about _copying_ the file on the server and then do a normal cvs remove in ext/standard? Then you'll have working checkouts and history. - Stig -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Moving output.c from ext/standard to main/
It's been bugging me for over a year now, and I'm now trying to figure out the best way to do it. output.c sits today in ext/standard, which is wrong, as it's really a part of the inner core of PHP, and not a set of functions. If I move the file in the CVS repository and fix the references, then everything would be fine, history would be retained, except checking out old CVS's will no longer work. If import the file into main/ and delete it from ext/standard, we lose the history for it, which is sucky. I'm thinking about moving the file in CVS, and in addition to fixing the HEAD branch, fix also the 4.0.6 branch, so that we at least can check out one version back. What do you guys think? Zeev -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Moving output.c from ext/standard to main/
On Fri, 20 Jul 2001, Zeev Suraski wrote: I'm thinking about moving the file in CVS, and in addition to fixing the HEAD branch, fix also the 4.0.6 branch, so that we at least can check out one version back. What do you guys think? +1 on this -Andrei Man, if you gotta ask, you'll never know. - Louis Armstrong, when asked What is jazz? -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Moving output.c from ext/standard to main/
It a shame that CVS doesn't have a way to handle things like this.. Are there commercial systems that can? -Jason - Original Message - From: Zeev Suraski [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, July 20, 2001 8:14 AM Subject: [PHP-DEV] Moving output.c from ext/standard to main/ It's been bugging me for over a year now, and I'm now trying to figure out the best way to do it. output.c sits today in ext/standard, which is wrong, as it's really a part of the inner core of PHP, and not a set of functions. If I move the file in the CVS repository and fix the references, then everything would be fine, history would be retained, except checking out old CVS's will no longer work. If import the file into main/ and delete it from ext/standard, we lose the history for it, which is sucky. I'm thinking about moving the file in CVS, and in addition to fixing the HEAD branch, fix also the 4.0.6 branch, so that we at least can check out one version back. What do you guys think? Zeev -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED] -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Moving output.c from ext/standard to main/
On Fri, Jul 20, 2001 at 04:14:21PM +0300, Zeev Suraski wrote: It's been bugging me for over a year now, and I'm now trying to figure out the best way to do it. output.c sits today in ext/standard, which is wrong, as it's really a part of the inner core of PHP, and not a set of functions. If I move the file in the CVS repository and fix the references, then everything would be fine, history would be retained, except checking out old CVS's will no longer work. If import the file into main/ and delete it from ext/standard, we lose the history for it, which is sucky. I'm thinking about moving the file in CVS, and in addition to fixing the HEAD branch, fix also the 4.0.6 branch, so that we at least can check out one version back. What do you guys think? makes sense. tc -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Moving output.c from ext/standard to main/
On Fri, 20 Jul 2001, Jason Greene wrote: It a shame that CVS doesn't have a way to handle things like this.. Are there commercial systems that can? Sure, any number of them. -Andrei C combines all the power of assembly language with all the ease of use of assembly language -- trad -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Moving output.c from ext/standard to main/
Jason Greene wrote: It a shame that CVS doesn't have a way to handle things like this. Are there commercial systems that can? You don't need a commercial system for this. I recently came by accident across subversion http://subversion.tigris.org/ I have yet to download and get a feel for it, but the website's feature list looks promising. For instance, it says Directories, renames, and file meta-data are versioned. Lack of these features is the most common complaint against CVS -- basically, CVS only versions file contents. Subversion will handle directory changes, file renames, and permission and other meta-data changes as well. -- Sebastian Bergmann Measure Traffic Usability http://sebastian-bergmann.de/http://phpOpenTracker.de/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Moving output.c from ext/standard to main/
On Fri, Jul 20, 2001 at 04:25:44PM +0200, Sebastian Bergmann wrote : Jason Greene wrote: It a shame that CVS doesn't have a way to handle things like this. Are there commercial systems that can? You don't need a commercial system for this. I recently came by accident across subversion http://subversion.tigris.org/ I have yet to download and get a feel for it, but the website's feature list looks promising. For instance, it says Directories, renames, and file meta-data are versioned. Lack of these features is the most common complaint against CVS -- basically, CVS only versions file contents. Subversion will handle directory changes, file renames, and permission and other meta-data changes as well. And its supposed to handle links, too. Great. - Markus -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Moving output.c from ext/standard to main/
On Fri, Jul 20, 2001 at 04:34:42PM +0200, Markus Fischer wrote: On Fri, Jul 20, 2001 at 04:25:44PM +0200, Sebastian Bergmann wrote : Jason Greene wrote: It a shame that CVS doesn't have a way to handle things like this. Are there commercial systems that can? You don't need a commercial system for this. I recently came by accident across subversion http://subversion.tigris.org/ I have yet to download and get a feel for it, but the website's feature list looks promising. For instance, it says Directories, renames, and file meta-data are versioned. Lack of these features is the most common complaint against CVS -- basically, CVS only versions file contents. Subversion will handle directory changes, file renames, and permission and other meta-data changes as well. And its supposed to handle links, too. Great. And it is far from even beta. Bad. -- / Alexander Bokovoy $ cat /proc/identity ~/.signature `Lead software developer and analyst for SaM-Solutions Ltd.` --- I'd rather be led to hell than managed to heavan. -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Moving output.c from ext/standard to main/
Wow, thanx. All my cvs gripes are answered. Can wait to use it when its stable. -Jason - Original Message - From: Sebastian Bergmann [EMAIL PROTECTED] To: php-dev mailinglist [EMAIL PROTECTED] Sent: Friday, July 20, 2001 9:25 AM Subject: Re: [PHP-DEV] Moving output.c from ext/standard to main/ Jason Greene wrote: It a shame that CVS doesn't have a way to handle things like this. Are there commercial systems that can? You don't need a commercial system for this. I recently came by accident across subversion http://subversion.tigris.org/ I have yet to download and get a feel for it, but the website's feature list looks promising. For instance, it says Directories, renames, and file meta-data are versioned. Lack of these features is the most common complaint against CVS -- basically, CVS only versions file contents. Subversion will handle directory changes, file renames, and permission and other meta-data changes as well. -- Sebastian Bergmann Measure Traffic Usability http://sebastian-bergmann.de/http://phpOpenTracker.de/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED] -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Moving output.c from ext/standard to main/
On Fri, 20 Jul 2001, Zeev Suraski wrote: I'm thinking about moving the file in CVS, and in addition to fixing the HEAD branch, fix also the 4.0.6 branch, so that we at least can check out one version back. What do you guys think? +1 on this +1 =) Peter -- *ZIMT - where PHP meets needs* Homepage: www.cyberfly.net - [EMAIL PROTECTED] PHP Usergroups: www.phpug.de - [EMAIL PROTECTED] Just for Fun: www.fist-center.de - [EMAIL PROTECTED] -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Moving output.c from ext/standard to main/
* Alexander Bokovoy [EMAIL PROTECTED] | | On Fri, Jul 20, 2001 at 04:25:44PM +0200, Sebastian Bergmann wrote : | I recently came by accident across subversion | | http://subversion.tigris.org/ | |I have yet to download and get a feel for it, but the website's | feature list looks promising. | | And it is far from even beta. Bad. However, progress is steady and pretty rapid, and the people involved are very competent and experienced. E.g. Karl Fogel, Brian Behlendorf and Greg Stein are three persons I'm glad to see behind this CVS-killer. -- Øyvind Møll [EMAIL PROTECTED] Initio IT-løsninger AS URL: http://www.initio.no/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Moving output.c from ext/standard to main/
On Fri, Jul 20, 2001 at 05:27:36PM +0200, Oyvind Moll wrote: * Alexander Bokovoy [EMAIL PROTECTED] | | On Fri, Jul 20, 2001 at 04:25:44PM +0200, Sebastian Bergmann wrote : | I recently came by accident across subversion | | http://subversion.tigris.org/ | |I have yet to download and get a feel for it, but the website's | feature list looks promising. | | And it is far from even beta. Bad. However, progress is steady and pretty rapid, and the people involved are very competent and experienced. E.g. Karl Fogel, Brian Behlendorf and Greg Stein are three persons I'm glad to see behind this CVS-killer. I know, my hopes rely also on this project. And main hope is that at least half a year will be worth to wait. :-) -- / Alexander Bokovoy $ cat /proc/identity ~/.signature `Lead software developer and analyst for SaM-Solutions Ltd.` --- Half of being smart is knowing what you're dumb at. -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Moving output.c from ext/standard to main/
Jason Greene [EMAIL PROTECTED] writes: It a shame that CVS doesn't have a way to handle things like this.. Are there commercial systems that can? Aegis handle file and directory rename operation and is Free. Read more here http://www.canb.auug.org.au/~millerp/aegis/aegis.html -- Walter Franzini, e-mail: [EMAIL PROTECTED] SysNet, Via Digione 8, 27100 Pavia - Italy -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Moving output.c from ext/standard to main/
On Fri, Jul 20, 2001 at 04:14:21PM +0300, Zeev Suraski wrote: It's been bugging me for over a year now, and I'm now trying to figure out the best way to do it. output.c sits today in ext/standard, which is wrong, as it's really a part of the inner core of PHP, and not a set of functions. If I move the file in the CVS repository and fix the references, then everything would be fine, history would be retained, except checking out old CVS's will no longer work. If import the file into main/ and delete it from ext/standard, we lose the history for it, which is sucky. I'm thinking about moving the file in CVS, and in addition to fixing the HEAD branch, fix also the 4.0.6 branch, so that we at least can check out one version back. What do you guys think? I'm pretty sure the correct way to do this is: Copy output.c,v from ext/standard/ to main/ 'cvs remove output.c' from ext/standard/ in the HEAD branch Update all affected Makefile's, etc. and commit them to HEAD That should preserve the file's history and retain compatibility with old versions / branches. -- Jon Parise ([EMAIL PROTECTED]) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Moving output.c from ext/standard to main/
At 12:27 PM 7/20/2001 -0400, Jon Parise wrote: On Fri, Jul 20, 2001 at 04:14:21PM +0300, Zeev Suraski wrote: It's been bugging me for over a year now, and I'm now trying to figure out the best way to do it. output.c sits today in ext/standard, which is wrong, as it's really a part of the inner core of PHP, and not a set of functions. If I move the file in the CVS repository and fix the references, then everything would be fine, history would be retained, except checking out old CVS's will no longer work. If import the file into main/ and delete it from ext/standard, we lose the history for it, which is sucky. I'm thinking about moving the file in CVS, and in addition to fixing the HEAD branch, fix also the 4.0.6 branch, so that we at least can check out one version back. What do you guys think? I'm pretty sure the correct way to do this is: Copy output.c,v from ext/standard/ to main/ 'cvs remove output.c' from ext/standard/ in the HEAD branch Update all affected Makefile's, etc. and commit them to HEAD That should preserve the file's history and retain compatibility with old versions / branches. We should do this in future too. We have renamed files in the past the *bad* way (just moving it in the cvs repository and not cp'ing it). Andi -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Moving output.c from ext/standard to main/
On Fri, 20 Jul 2001, Zeev Suraski wrote: That sounds like a pretty cool idea! Btw, you can also manually remove the old tags from output.c,v after copying it.. - Sascha Experience IRCG http://schumann.cx/http://schumann.cx/ircg -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
