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

Re: svn delete

From: Edward Diener <ediener_at_loyaltyworks.com>
Date: 2004-08-16 16:43:47 CEST

"Wadsworth, Eric (Contractor)" <wadswore@fhu.disa.mil> wrote in message
> > I did a svn checkout from a repository to a directory and that worked
> > correctly. I did this as a test of some code I am writing in
> > Python. I now
> > want to delete the directory from under svn control
> Do you want to:
> 1. Get rid of your working copy?
> 2. Stop version control on your working copy, but retain the files
> 3. Remove this directory from the repository?
> Answers:
> 1. If you want to get rid of your working copy, just delete the working
> using standard OS commands.
> 2. Do an svn export to clean out all subversion stuff (.svn directories)
> make a clean tree from that working copy. Then delete the working copy,
> rename the exported tree to the same name as your old working copy. There
> you have a clean directory, no longer under version control.
> 3. As others have said, to remove a directory from the repository, the
> subdirectory name must be removed from where it lives. This requires that
> you either specify it directly to the server in the form of a URL, or have
> the parent directory checked out as a working copy so you can delete this
> subdirectory from it via svn delete. Make sense?

Yes, it does. Thanks for your reply. It finally dawned on me that the
repository has no idea what working directories exist on different client
systems, but only of its own internal filesystem. Now I understand that 'svn
delete ...' is actually deleting a filesystem entry in the repository. It
has taken me awhile to wrap my mind around this model but I think I finally
have gotten it.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 16 16:44:34 2004

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.