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

RE: switching added files -- Re: What revision should an added not yet commited node have?

From: Bert Huijben <bert_at_qqmail.nl>
Date: Tue, 23 Mar 2010 23:53:52 +0100

> -----Original Message-----
> From: neels [mailto:neeels_at_gmail.com]
> Sent: dinsdag 23 maart 2010 19:13
> To: Greg Stein
> Cc: Julian Foad; dev_at_subversion.apache.org
> Subject: Re: switching added files -- Re: What revision should an added
> not yet commited node have?
>
> On 22 March 2010 17:20, Greg Stein <gstein_at_gmail.com> wrote:
> > I think the child is *always* a child of the parent.
>
> Greg, you definitely know that this works today:
>
> [[[
> $ svn add bar/y
> A bar/y
>
> $ svn ci -mm
> Adding bar/y
>
> $ svn switch --depth=empty '^/foo' bar
> At revision 1.

Note that while this might be/look supported... it is also a typical example
which triggers issue #3569.

You switch the directory to a new revision, but don't update its list of
children to match that revision. So you will never receive the children of
the node, even if you perform svn update --set-depth infinity.

(There is no way to fix this situation except switching this node back to
its original location_at_rev with depth empty and then performing the switch
recursively)

        Bert
Received on 2010-03-23 23:54:34 CET

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