[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Delete in repository but not in working copies

From: Olivier Sannier <olivier_at_obones.com>
Date: Fri, 28 Mar 2008 15:18:35 +0100

Hi all,

We just did a migration from another SCM to SVN and we just discovered
that some files in the repository should not have been there in the
first place. Before the migration we spotted some of these already but
unfortunately, a good number went through.
I thought of deleting them with the "svn delete" command but in most
cases, this is not desirable as it will mean the file is also deleted
from the users working copies the next time they do an update. Indeed,
these files, while they must not be in the repository, must stay on the
users computers as they contain their own local options. Their contents
may or may not be different from what currently is in the repository,
but in all cases it will break compilation if they are removed.
Recreating them can be quite cumbersome and considering the number of
occurrences (number of files * number of users), I'm looking for a way
to remove the file from source control so that it won't appear as
modified on users machines while not deleting it at all.
I have searched through the archives and found this post which is
exactly what I need:

http://subversion.tigris.org/servlets/ReadMsg?listName=users&msgNo=51125

However the proposed solutions work well if applied before the fact, but
not when the file is already in the repository. Since this request was
made quite a while ago, I'm wondering if anything changed in this area.
If so, how can I achieve what I described above?

Thanks for your help
Olivier

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-28 15:19:14 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.