Vladimir Marek writes: > ... > > and another one, how do we reparent ?
Mercurial actually works quite a bit like Teamware with respect to parent/child workspace relationships, but it's easier to use. With Mercurial, you specify the 'paths' you want for the gates you deal with, either on the command line or in the .hg/hgrc file. If you do the latter, then you can set up multiple paths for gates you use often with a given workspace. Here's an example from one of my workspaces: [paths] default=ssh://carlsonj at hg.opensolaris.org/hg/rbridges/rbridges-on on=ssh://anon at hg.opensolaris.org/hg/onnv/onnv-gate This lets me do "hg pull" and get my RBridges project gate by default. If I want to pull directly from ON (equivalent to reparenting and bringing over for a merge), I just do "hg pull on". > Do we reparent at all (will there > be master and clone gates ?) That need goes away. Mercurial doesn't put long-lived locks on the gate while reading or writing. (It may still be worthwhile to have clones for sites that have bandwidth issues, but not to solve the reader/writer problem.) -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
