Why not build these features into CVS directly? It'd save an enormous amount of runtime overhead.
--- Forwarded mail from [EMAIL PROTECTED] In article <[EMAIL PROTECTED]>, Matthew Herrmann wrote: >hi all, > >what do people think about the idea of a project which sits on top of cvs >and provides another level of abstraction to branching, merging, revision >management etc. I'm working on one already, but with a different initial focus from what you are proposing. I have no short range plan to do anything with tags. I call the system MCVS (Meta CVS). My present concern is to create a layer which adds directory structure versioning, and sane behavior for the renaming of files. I have a workable basic design and am just going through the implementation a little bit at a time. The ``mcvs import'' operation already works. >My idea was to do it in a compilable scripting language, (python -- my >choice, perl, vb (just kidding)) and that it would call cvs behind the >scenes. Working in Common Lisp here. :) --- End of forwarded message from [EMAIL PROTECTED] _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
