Well, yes. The "empty" depth on the parent means, for example, that if
another working copy creates and commits a new child, 'svn up' won't
pull it.
Note the reverse problem can also happen: a depth=immediates parent
and a depth=exclude child.
So, yes, it's by design. Maybe we could change the
Hi,
If I update a folder with -set-depth=empty and then update a child folder with
-set-depth=infinity the parent is still reported as having empty depth by svn
info. This is with svn 1.7.6.
Is this by design? Seems weird to me...
James
