I'm trying to get my development project in php/javascript into cvs.
My project has this directory structure:
/
somefile.html
otherfile.php
/modules
files.*
/doc
files.*
/someotherdir
otherfiles.*
/config
custom_config.php
The problem i'm facing is that custom_config.php file contains generic
config values that needs to be modified by every developer/user to get the
software working, but I don't want that nobody updates the repository with a
custom user/passwd pair, for example, inside custom_config.php when doing a
commit. So I suppose that if any developer that issues a commit, tries to go
through it on a file by file basis, everything would go ok but what about a
commit with cvs recursive behavior?
My question is: is there a way to prevent a file/directory from being
commited when someone does a "project wide" commit?
Thanks in advance.
Luis.
PD: Sorry about my poor english
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
