On Jun 30, 2006, at 07:15, T. Wassermann wrote:
> In a repository somebody checked in the file config.inc.php. This
> file contains some configuration settings that are different for
> every local machine.
>
> Now it wouldn't be efficient if anybody can commit the own version
> of this file. We have to remove it from the repository with svn
> delete, but: We don't want to delete it from the wc's when the
> users calls svn update.
>
> It would be nice if we can:
>
> - call svn delete with an switch like --no-wc-remove
>
> - the file will be deleted from repository, the *physical file* in
> the working copies will not be removed - the file is no longer
> under version control, right - but the file exists, the users have
> not to recreate it. After this operation somebody can add this file
> to svn:ignore.
>
> So this problem a colleague have had too - I think it happens
> sometimes, you're adding file to version control and later you
> mention that's bad if this files are under version control, but
> you'll not remove this file from the existing working copy
> directories...
Subversion doesn't offer that. This is a suggested way to handle this
situation:
http://subversion.tigris.org/faq.html#ignore-commit
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 30 12:40:35 2006