On Tue, Feb 06, 2007 at 03:49:45PM -0500, Bill Sommerfeld wrote: > that sounds fundamentally incompatible with the notion of branching as > implemented by most other SCM systems. How do we put a fence around > this bottomless pit?
I don't know of a way. Note that the mercurial community seems to have a passion for symmetry and the lack of defaults. It took them a long time before they finally made a clone record the path to the parent repo so that you wouldn't have to specify a repo for future pulls. They generally recommend using separate trees for maintaining branches (with which I agree, at least for projects), and all such branches have names (the repo URL). I think it's a bit naive and extreme, but I may be mischaracterizing them to some extent. Now, we can enforce conventions on push -- non-mainline branches are generally closed -- but preventing screwups before that may be difficult, depending on how much we want to rely on cadmium getting things right for you. Danek _______________________________________________ tools-discuss mailing list [email protected]
