It sounds like the OP knows that this isn't a current feature, hence the
Feature Request. What he is noting is:
1. A places a file into version control.
2. The file is not a good candidate for being version controlled (in
this case because everyone has a different copy of it)
3. He would like to have SVN silently remove the file from version
control, but preserve the copy that everyone has in their WCs.
Yes, the template is the correct thing to do, if it was thought about
before hand, however, this is a case where users are trying to overcome
a mistake that a developer made. This mistake, in large teams is can be
very costly to over come especially, if you have to tell everyone and
have the do the manual copy file to temp loc, update, copy it back.
Especially since we all know that devs will read and follow all their
email before doing the next update....
This is a convenience request for making SVN more scalable, and offering
recovery solutions when folks put something into VC that shouldn't be
there.
Casey
-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2006q2@ryandesign.com]
Sent: Friday, June 30, 2006 5:39 AM
To: T. Wassermann
Cc: users@subversion.tigris.org
Subject: Re: (Feature request?) svn delete only in repository
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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 30 16:52:31 2006