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

RE: Re: Problem deleting file, then parent directory

From: Richard Biffl <tigris_at_blacklettersoftware.com>
Date: Sun, 8 Aug 2010 01:08:07 -0700 (PDT)

> This is a known situation for SVN (I wouldn't call it an issue, as the
> reason its happening is quite valid).
> When a commit is completed, only those items directly involved in the commit
> have their "last modified' revision number in the working copy bumped. In
> your example, file1 is deleted (and so has no last modified revision).
> However, SVN cannot automatically move the last modified revision of dir1 to
> 5, as there may have been further changes to file2, for example, that need
> to be brought into the WC. The only way that dir1 can be considered
> up-to-date is for an SVN Update to be run on it.

OK, thanks, Daniel. I see that the commit of the directory deletion is accepted if I SVN Update my working copy before I TortoiseSVN Delete the directory that contained the now-deleted file.

So, after I TortoiseSVN Delete a file, I need to SVN Commit the change, then immediately SVN Update the working copy so the deleted file won't be expected. It would be nice if this were done automatically. It's not at all intuitive that, after using SVN Delete in my working copy, I still need to run SVN Commit *and* SVN Update to tell the working copy that the file was deleted.

I saw that, if I do not SVN Update after the first file deletion, my SVN Commit of the directory deletion fails and I'm told to update my working copy. But I am then unable to do an SVN Update because of the tree conflict. The only way I saw to resolve the situation was to use TortoiseSVN Resolved.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-08-08 10:40:23 CEST

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

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