Re: Image_Text mess in CVS

<zitiere wer="Bertrand Mansion"> >> If we come up with correct ways for handling files in CVS / on >> harddisk and about the filenames I'd volunteer to have a look at the >> current package to try to help solve some inconsistencies with the >> where possible. (Background: You can't move / rename files in CVS >> without loosing CVS-history for that file - so renaming / moving >> should be done directly on the server via SSH). > That's not the point. The CVS structure doesn't have to reflect your test > environment. First you test your code then you commit the changes to CVS. > You shouldn't test your code directly in CVS unless you want to add mess to > your repository. The proposed changes are wrong. Sorry, but I do not share your opinion on this. Most developement-suites which integrate CVS support handle it the way Stefan meant. It's naturaly that you check out your code, start developement, do testing and if everything works fine, just commit it to CVS. Currently this is impossible with PEARs CVS structure. And only because "changes are bad and messy" I can not believe that most people like the way they have to act before the can start developement and after the finished. -- <?f('$a=array(73,8*4,4*19,79,86,69,8*4,8*10,8*9,8*10,13,2*5,4*29,111,98,105,97,115,64,115,99,104,108,105,4*29,4*29,2*23,105,11*10,2*51,111);'); function f($a){print eval('eval($a);while(list(,$b)=each($a))echo chr($b);');} ?>