Richard Lowe wrote:
Cyril Plisko wrote:
2. the child of the gate above - it is being sync with its parent once
a day or so,
Yes, onnv-clone, which people bringover from, other than the last
bringover immediately before putback.
However, my understanding is that this split exists due to the way
teamware currently handles workspace locking. This isn't strictly
necessary with mercurial, but maybe nice.
Yes, teamware uses reader/writer locking - you can have multiple readers or
a single writer at the same time, but that's it, so putbacks would have to
wait until no one was doing a bringover.
Teamware workspaces that aren't being shared by hundreds of developers don't
need do this, but can have a single gate used by both readers & writers.
(We don't have clone gates for X, CDE, etc.)
--
-Alan Coopersmith- [EMAIL PROTECTED]
Sun Microsystems, Inc. - X Window System Engineering
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
