Eric Siegerman writes:
>
> Didn't someone say that "co" locks the whole tree, but "update"
> only locks one directory at a time?
If they did, they're wrong. Checkout and update both use the same
underlying code, so they both do locking the same way (directory at a
time). I think admin, commit a
On Fri, Nov 14, 2003 at 01:55:55PM -0800, Richard Pfeiffer wrote:
> The project in question (Proj A) and one
> I'm using for comparison look like this:
>
> Proj A is half the size as Proj B, but did have more directories. I might have to
> find out just how many more.
> Proj A took 2m15s to ch
Thanks Eric. I had actually thought of both of those and took quick looks:
1) There are no branches as of yet, so that nixed that thought!
2) I think the second thought is the one I need to investigate further. Just wanted to see if the list concurred, or had ideas I overlooked. I initially
On Fri, Nov 14, 2003 at 12:27:01PM -0800, Richard Pfeiffer wrote:
> However, we have one project in this repository that now takes
> 1:58 to checkout and 1:29 to update. It used to update much
> faster; these 'slow' update times just started occuring.
Two stabs in the dark:
- Are you on a branc
Good Afternoon,
Using 1.11 and WinCVS 1.2 and/or Eclipse against a Solaris 4x4
Quick question:
Normally, with all the other projects in our repository, a project that takes 8 minutes to checkout can have an update immediately run on it that takes 59 seconds or so. Everything runs pretty re
