Mark J. Nelson writes: > That makes pretty good sense for a branched development model, too. We > don't use that, but others may. And if you manage multiple releases via > branching, you shouldn't need to force a pull to get the contents of the > parent (or master) repo. But it might still be sensible to require force > to CREATE such a branch in the first place.
Yes, I think that's the underlying issue that meem was asking about: multiple heads are useful for handling branches. We historically do "branching" in [Open]Solaris by simply copying over to a new repository and starting anew for each release, but for the basic Mercurial tool set, there's no reason that should be the *only* way to do things. Thus, it supports it intentionally, and you can trip over that support if you do "bad things," like doing work right inside your own project gate, rather than doing push/pull to gates and the work outside. -- 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
