This was what I was thinking too. I have lot of stuff which is not (yet) added to CVS. Wouldn't this script delete all those too?
The current cvsclean ONLY deletes the files which are not in CVS and are mentioned in .cvsignore. Much safer that way. If there are files that are not mentioned in .cvsignore files you'll get a list of them by doing 'cvs update' (The ones marked with '?' :) -1 from me for changing this. Fix the .cvsignore files instead. --Jani On Fri, 2 Nov 2001, Markus Fischer wrote: >On Fri, Nov 02, 2001 at 03:15:09PM +0100, Hartmut Holzgraefe wrote : >> i'd expect running cvsclean gives me exactly the set of files >> i'd get from a fresh checkout and nothing more, and that definetly >> isn't the case with the current cvsclean while it is with my >> alternative > > I'd expect running cvsclean cleans up the source tree in a >way it *works like* a fresh cleanout. But I don't want my private >files floating in the tree (like some private testing c sources, >some diffs and what else) to be deleted when they don't influence >the configuration/compilation. Thats why we have cvsignore file. >Probably they weren't adjuested and should be fixed. > >Sounds reasonable? > >- 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]
