Thanks Conrad! I think I could implement a script that checks for restricated file names in the commit being issued and returns a non-zero in some cases. But what about this scenario:
1. Server must accept all changes from developers that commit changed files 2. Developers should take care of what they're commiting so that they can change that custom_config.php when they want to. I think this could be implemented commiting just the desired files without recursion but I wonder if there's something like the file .cvsignore that applies to updates and checkouts but not to commits. In that case being a developer I could write a .cvscommitignore file containing the files of my working copy that I don't want "cvs commit" to consider when used recursively. Thanks again. Luis. Mensaje citado por "Conrad T. Pino" <[EMAIL PROTECTED]>: > > My question is: is there a way to prevent a file/directory from being > > commited when someone does a "project wide" commit? > > http://www.cvshome.org/docs/manual/cvs-1.11.14/cvs_18.html#SEC165 > > > Thanks in advance. > > You're welcome. > > > Luis. > > Conrad > > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
