> > Third, I seem to recall that your branch code hints at a fifth
> > possible depth, -1 "missing". Do you still plan to implement and
> > expose this functionality? It sounds useful to me.
> So far that's for internal use only, not meant to be exposed to the
> user. Thus, I don't know what functionality you had in mind :-).
Just as the user can override a directory with depth 'empty' or 'files'
by pulling in child entries explicitly, he should be able to do the
opposite: exclude a specific child of a directory while including other
children, including new children in updates. The exclusion would be
sticky, by storing a depth=-1 entry for the child in .svn/entries.
Whether/how it should be displayed by 'svn st' is more than I can say
One can achieve a similar effect by setting the subdir to depth 0, but
that only applies to dirs, not regular files. And in some sense,
having a subdirectory _missing_ from your wc is more honest and less
confusing than having it present but empty.
Received on Fri Nov 3 14:37:09 2006