use case for config files in repository

I have a question regarding configuration files in a repository.
Assume that I have a configuration file just as log4j.properties or
some database connection configuration file. Now, this file needs
to be in the repository because it is relevant to the project, but
certain fields in the file change, like username and/or password or
perhaps logfile location based on the computer on which the program
is running. After I checkout a version of the repository onto a
computer, would there anyway to tell subversion that I no longer
want to consider this file when updating or committing?

Dan

-- 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
Daniel Allen, <dan@mojavelinux.com>
http://www.mojavelinux.com/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
"While they're pumping, you're soaking them" 
 -- Speed Loader TV Advert
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org