subversion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bert Huijben" <b...@qqmail.nl>
Subject RE: switching added files -- Re: What revision should an added not yet commited node have?
Date Tue, 23 Mar 2010 22:53:52 GMT


> -----Original Message-----
> From: neels [mailto:neeels@gmail.com]
> Sent: dinsdag 23 maart 2010 19:13
> To: Greg Stein
> Cc: Julian Foad; dev@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@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@rev with depth empty and then performing the switch
recursively)

	Bert


Mime
View raw message