Re: Partial checkouts on a huge project

On 4/28/06, mike nicholaides <mike.nicholaides@gmail.com> wrote:
> Yeah, I thought about recursively doing non-recursive checkouts, but
> that's a pain.
>
> Another problem that I forgot to mention was that when you I have a
> huge project, svn status and commits take a really long time. I was
> considering making a super-simple web-based mechanism to view the
> status, commit, update, etc. So, I would ideally want it to be a
> quick operation.

svn status will become *a lot* faster in 1.4 (which is - I hope - to
be released soon). We have a lot of working copy library fixes in that
version which should generally make your wc-actions a happier
experience.

svn status depends on file modification times as a shortcut not to
have to check file contents. After some time, those times may get out
of sync with what's in the .svn area. Running 'svn cleanup' will
update the .svn area and may speed up svn status again.

> Well, if I can't find an elegant solution for the my problem, I will
> do what you suggested, David. Thanks.
>
> Anyone got any bright ideas?

Yes, help us fix the real problem :-) (is it issue #695?)

> Thank you all,
> Mike

bye,

Erik.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jul 4 11:44:32 2006