On Sun, Oct 5, 2008 at 2:57 PM, Listman <listman_at_burble.net> wrote:
>...
> scanning the filesystem is not an option for larger repositories, svn
> update, status etc
> already take 20 mins for some of my repositories, i'm really hoping that we
> can resolve this
> with wc-ng
Unless I've totally forgotten something, "svn update" won't scan *at
all*. It'll read the SQLite database, see what versions you have, and
send that to the server. There is no need for ... oh darn. Just as I
say that, I remember missing directories/files. We need to look for
stuff that's missing, which is thankfully a more limited task than the
current scanning.
For svn status, I want to have a mode that is "give me something
close". It will just show you the state of the WORKING tree, and not
hit the filesystem beyond the SQLite database. It'll show you all the
adds, copies, deletes, etc. If you use "svn edit", then it will also
show administratively-edited files. And... if you do a normal "svn
status", then it can update the database with seen-edits so the next
time you do the "quick" mode, it will also show those (tho they may be
stale if you edit a file back to pristine).
svnversion will definitely avoid scanning. That is just reading the
versions out of the SQLite database. I did that test code in the
branch, and it all looks good.
Checkouts for large repositories could be fast if you have multiple
WCs from the same repos, *and* you use a central datastore. In that
case, it will skip asking the server for content, and just fetch it
from its system-wide set of pristine files.
So... yah. There should be a ton of improvements in day-to-day work.
Cheers,
-g
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-10-06 08:30:39 CEST