I had a question regarding the 'cvs remove' functionality. What's the reasoning behind not allowing a 'cvs remove <folder>'? It would seem to me that it'd be quite logical, and useful to have in the system and doesn't seem to be a huge difference from the 'cvs remove <file>', although granted it'd have to handle a recursive case for folders within a folder, but that would be a more general case that one could take care of with a nice error message if too complex... like "Sorry, this folder has other folders contained within. Please remove all other folders before removing this folder." or something to that effect. Maybe I'm just overlooking something but it would seem to me that this would be very useful... Granted I haven't been using CVS a long time, but can't seem to find the answer to this anywhere. There are of course counter-points to this that I've thought about like: (a) What about other developers that are working on a file in the folder/package you're trying to remove? Of course, in this case you would have to have some kind of way to turn off the functionality for larger software projects if you absolutely wanted to make sure that no-one had the ability to remove entire packages for instance. But for a group that communicated about stuff regularly, and for general architecture changes where packages become outdated, it sure would be nice to remove them from a tree. Thanks, -Jason ------------------------ Jason Childers ([EMAIL PROTECTED]) Software Engineer Troba, Inc.
