On Jun 22, 2007, at 12:35, Joep Suijs wrote:
> I have a large set of development files (sources of
> different projects and some tools) in a directory tree
> on two different PC's and I want to use subversion
> (and tortoisesvn) to achieve two things:
> - version control over the sources and tools.
> - keeping those trees in sync.
> It looks like subverions can do this (although I have
> to avoid a commit on the whole tree - this takes an
> hour due to the large number of files and size). But
> there is one thing that surprises me.
> If I do a delete on a file or directory from a workset
> and a subsequent commit, this file (or directory) is
> removed from both the workset and repository. But when
> I do an update on the other machine, it does not
> remove the file but only removes version control.
> Is this expected behavior, can this be changed or am I
> missing something?
If your local copy of the file has uncommitted modifications, and you
"svn update" and the update would remove that file, then Subversion
does not delete the file, because it is Subversion policy to not
destroy your work irretrievably, which is what would otherwise occur.
If you do really want your uncommitted changes to get thrown away,
you can either "rm" the file after updating, or "svn revert" the file
before updating.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jun 23 11:47:20 2007