Re: Ignore local changes?

[Steve Madsen]

Wade Williams wrote:
> 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.

You're not the only developer that has had to deal with a problem like this. 
 I agree with others who have said that allowing CVS to circumvent its own 
controls is not a wise idea.

My advice is to be more specific when you commit.  You don't need to commit 
from the top-level of your project.  You likely already know where you made 
changes you do want to commit.  If you've arranged your tree well, this 
configuration file should be somewhere else.  In this case, commit closer to 
the real changes and CVS won't try to also commit your configuration changes.

If you happen to make changes in the same place as the configuration file, 
then commit files one by one.

--
Steve Madsen <address@hidden>
Tadpole Computer, Inc.  http://www.tadpole.com