Ababccc <[EMAIL PROTECTED]> wrote: > I'm wondering what people usually do, in case there is a project on CVS > which uses a C++ library which is in a completely separated CVS.
> If the library gets changed (for its own purposes) the project might get > screwed... In cases like that, I equip the client project with a big fat README file that explains how to check out a *specific release* of the library in a subtree. The subtree ends up with a sticky tag and a normal "cvs update" doesn't affect it. _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
