Um,
I hadn't realized that there *was* an ongoing discussion of CM systems. Was this on cap-talk, and have I fallen off that list somehow?
I used to work for a CM vendor called "teamone", whose product was called "teamnet."
Teamnet consisted for the most part of a versioning file system (TOFS), a copy-on-write file system, and tools for migrating sets of changes between work areas. The change sets were called "ECOs" for Engineering Change Order.
With teamnet, there wasn't really a concept of "checking out" code from the repository. You'd make a virtual copy of the repository, (your Work Area) and then treat it like a normal UNIX filesystem. Any time you wanted to remember it as was, you would drop a checkpoint.
To move code between your work area and the baseline (another work area, actually) You'd list the changed files in an ECO, and apply the ECO to the baseline (assuming you had the privileges.)
-jcr
> "Jonathan S. Shapiro" wrote:
>
> On reflection, discussions about a configuration management system
> don't belong on eros-port either, so I have started a new list. Unless
> I made a mistake, it includes only those of you who have participated
> in the discussion plus Bill Frantz and Jonathan Adams.
>
> If you prefer not to be involved in discussions on DCMS, please feel
> free to unsubscribe, but do consider giving it a week or two, as the
> early concerns I have center on naming issues.
>
> Thanks
>
>
> shap