Re: vc-svn-dir-status

[Nick Roberts <nickrob@snap.net.nz>]

 > > In response to bug#2117 I suggested that I suggested that vc-stay-local-p
 > > need not be slow if vc-svn-registered need parsed the SVN controlled
 > > text-base directory instead of executing "svn status -v DIR".
 > 
 > That would be a good change.  Many VC backends do similar things to
 > speed up this common operation.  Tho, admittedly, this is usually done
 > for files rather than for dirs, so there might be unexpected problems.

Maybe the text-base directory is irrelevant but I've tried to understand why
"svn status" gets called twice in this case.  I think in this first case,
vc-local-p -> vc-registered -> vc-svn-registered it just needs the status of
one file, namely the directory, and it needn't recurse.  If that's so "svn
status -v -N DIR" would presumably be quicker and only the first line need be
parsed.  vc-cvs-registered does nothing in the case of a directory argument,
presumably because, in CVS, directories aren't under version control.

To add to my confusion I don't understand the documentation string of
vc-svn-parse-status:

   ...Unless FILENAME is non-nil, parse only information about FILENAME and
   return its status.

It always appears to be non-nil but if it was nil how could you parse
information about it?

-- 
Nick                                           http://www.inet.net.nz/~nickrob