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

Re: Possible bug in nightly build

From: Robert Dailey <rcdailey_at_gmail.com>
Date: Mon, 29 Jun 2009 08:00:37 -0500

On Mon, Jun 29, 2009 at 3:14 AM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:

> Robert Dailey wrote:
> > I'll do my best to describe the steps to reproduce. Information
> > regarding version numbers and my PC are at the bottom.
> >
> > 1. Find a versioned directory in your WC that contains other
> > versioned directories and files under it.
> > 2. Add some new files and change some existing files under this
> > directory.
> > 3. Commit the directory that contains the modified/added files in it
> > 4. After the commit completes and without doing an update, SVN Delete
> > that directory.
> > 5. Try to commit the delete.
> > 6. It fails, saying it needs to be updated.
> > 7. Do an update. You get a tree conflict.
> > 8. Delete the deleted directory (It should still be there with an X
> > overlay).
> > 9. Do an clean/update a few times, revert the delete, and update
> > again. Notice how it isn't pulling down that directory again. You
> > actually have to delete the parent of the deleted directory and do
> > another update at a higher level in order for it to pull down that
> > directory again so you may try to delete it once more.
> That's expected: the 'depth' is changed to 'this item only' when you
> delete a folder.
> To get such a folder back, you have to use the "update to revision"
> dialog and specify "fully recursive".

So you're basically telling me this is a subversion-specific issue, and if I
wanted to see this handled a bit more intuitively then I would have to
contact them? Fair enough. I just think the behavior is a bit confusing and
broken and could be improved.


To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-06-29 15:00:50 CEST

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

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