On Tue, Oct 28, 2008 at 4:53 PM, Justin Erenkrantz
<justin_at_erenkrantz.com> wrote:
> On Tue, Oct 28, 2008 at 10:01 AM, Ben Collins-Sussman
> <sussman_at_red-bean.com> wrote:
>> productivity. Very few opensource projects are that large. But in
>> the corporate world (where both perforce and subversion are intensely
>> used) these huge working copies just aren't that unusual. At Google,
>> our main source tree is gi-normous... we would be *dead* if perforce
>> had to walk the tree to tell me which files I had changed. Heck,
>
> Yah, but the Perforce model gives back all of its speed advantages
> when you try to commit. I remember 30+ minutes trying to submit a
> single file change when using Perforce. (IIRC, Perforce walks all of
> the workspaces at *commit* time.)
Umm, for what it's worth, I suspect your Perforce install was rather
atypical. Most Perforce servers are relatively zippy when submitting
changes.
-garrett
---------------------------------------------------------------------
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-29 00:50:25 CET