Toby Johnson wrote:
> We have a web site checked in to Subversion which includes some
> behind-the-scenes config files. When I make changes to this site, I
> first test those changes in a development directory.
>
> The development version of these config files point to a development
> MySQL database, but the production version of course points to the
> production database. So every time I want to commit changes from the
> development area, svn sees these config files as modified, but I don't
> want to check those changes in.
>
> Is there some clever way to get svn to not notice these changes in the
> development working copy? Currently I have to explicitly specify each
> file I want to commit so it doesn't pick up the unwanted changes as
> well. I guess I could write a shell script to temporarily swap out the
> config files if nothing else. Has an "exclude" option to "commit" or
> "status" ever been considered?
It sounds like
http://subversion.tigris.org/project_faq.html#ignore-commit
is applicable to your situation.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 14 14:55:40 2004