Re: recursive/nonrecursive

On Wed, Jul 03, 2002 at 03:08:16PM -0500, Ben Collins-Sussman wrote:
>
> So I'm working on issue #493, started by pilchie long ago.

Okay, so I ran out of steam...
>
> checkout recursive --nonrecursive
>
> Yes, you can check out a nonrecursive working copy... but does
> this feature acutally work as we want it to?
>
> - 'svn co -n URL' effectively creates a wc of the directory of
> depth 1... contains only immediate *file* children, and that's
> it...
>
> - Yes, you can commit changes to the file-children.
>
> - Updates don't work, assuming things changed below your wc.
>
> I'm worried about this feature, because it feels half-implemented
> to me. I mean, the entries file has *no* idea that its list of
> children is incomplete, or that it's in some 'nonrecursive' mode.
> Ideally, updates on areas below the top-level dir should be
> ignored by the update-editor, or something. Maybe a depth
> argument needs to be marshalled all the way over the network to
> dir_delta... not sure.
>
> Should we remove this feature? If not, how should we finish it?
>
See http://subversion.tigris.org/issues/show_bug.cgi?id=695

"svn checkout --nonrecursive should be sticky"

Also what about the idea of adding the depth enum, and making commands able to
operate on:
depth 0 == entry only
depth 1 == entry + file children
depth infinity == entry + all children recursively

The problem is that right now non-recursive is a mix of depth 0 and depth 1,
and we have no way of performing the other way.

take propset for instance. There is no way to set a prop on a dir + all of
its file children. It's either the dir only, or fully recursive.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kevin Pilch-Bisson                    http://www.pilch-bisson.net
     "Historically speaking, the presences of wheels in Unix
     has never precluded their reinvention." - Larry Wall
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~