On Jun 19, 2005, at 10:43 AM, Avi Bryant wrote:
... I'm not really sure what you mean by "no merging to worry about later". It's perfectly possible, for example, to maintain multiple branches in multiple repositories and be constantly merging between them. Or to have the same versions mirrored across multiple repositories. Or to have some versions in a particular branch in one repository, and some in another, etc. It's probably best in this context to think of repositories more like tags: putting something in the release repository means you're tagging it as "releasable". But it might have been a version that you originally committed to an internal development repository and copied over. Monticello is much more flexible than CVS for that kind of thing because each version carries with it all the ancestry metadata it needs, and a repository is just a collection of individual versions + access rights. Does that clarify things somewhat?
Yes, I forgot that a version (no matter in what repository) carries its ancestry metadata, which is a nice feature.
- Doug