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

[Subclipse-dev] Re: [Issue 1646] Synchronize and Update of a new Directory with new Files failed

From: Stephen Elsemore <selsemore_at_collab.net>
Date: Fri, 19 Feb 2016 18:13:31 +0000

On Fri, Feb 19, 2016 at 5:06 PM, <markphip_at_tigris.org> wrote:

> ------- Additional comments from markphip_at_tigris.org Fri Feb 19 09:06:30
> -0800 2016 -------
> What Steve means is you cannot update a file without also having its
> containing folder. So since you do not
> have the folder at all, you just see the folder as an incoming change and
> it is assumed you will get anything
> beneath it too.
> We do need to make sure that there is not some scenario where updating the
> folder brings it in as
> depth=empty.
> Generally, we tend to update from the root of our project so just do not
> run into things like this.

I did experiment with trying to find a way that updating could bring a
folder in as depth=empty. I tried updating at various levels, updating
folders with property changes, etc. I couldn't find any scenario that
caused this to happen, except for using the "Update to version..." option
and explicitly selecting that level. If anybody discovers a recipe for
such a problem, please post it.

Maybe we can revisit the feasibility of showing the children of the new
folder in the synch view. I do notice that from the command line 'svn
status -u' does include them (I wonder if this has always been the case).


To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_subclipse.tigris.org].
Received on 2016-02-19 19:19:57 CET

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

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