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

Re: Possible data loss after commit on Win32

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-09-25 05:12:44 CEST

"Francois Beausoleil" <fbos@users.sourceforge.net> writes:

> issues/
> assigned/
> fbos/
> 0003/
> resolution/
> resolved/
> Then, I did the following:
> svn delete assigned/fbos/0003/resolution
> svn move assigned/fbos/0003 resolved

There's no data loss here, there's just some confusion about what you
scheduled in your working copy.

1. you scheduled assigned/fbos/0003/resolution for deletion.

2. when you ran 'svn move assigned/fbos/003', that was equivalent to

     - svn copy assigned/fbos/0003 resolved/0003
     - svn rm assigned/fbos/0003

  So the copy is now a schedule add, with *local* changes within it:
  the deletion of 'resolution'.

> K:\jobnudge-issues>svn commit
> Deleting assigned\fbos\0003
> Adding resolved\0003
> Deleting resolved\0003\resolution
> Deleting resolved\0003\status.txt

And that's exactly what the commit did.... except for that last line.

I think you probably scheduled '0003/*' for deletion, rather than
'0003/resolution'. It's not like the filesystem "lost" your
status.txt file. The commit explicitly deleted it, meaning it was
scheduled for addition.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 25 05:14:16 2003

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.