>>Always, and only ever, modify a copy of any file if you don't want CVS >>to see your changes to it! > >I can't imagine I'm the only developer that makes local changes to try something out, >but wants to be sure those changes do not end up in the repository.
Maybe you could setup your system that on every update (at least of this file) it makes a copy of the checked out file. You would then work with the copy and on commit the original file is still intact. And on next update your local changes get overwritten again. That way your changes don't get committed (well, you looe all of them) but you still get updates to the file. If your app expects a special name for this file you need to rename it for cvs (like myfile_template or myfile_original) so the generated copy can have the expected name. bye Fabi _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
