> -----Original Message-----
> From: Earl Williams [mailto:[EMAIL PROTECTED]]
>
> "Pierre Asselin" <[EMAIL PROTECTED]> wrote in message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > Adapt your tree structure. Do *not* mix files from teams A
> and B in a
> > single directory, CVS won't handle that well.
>
> Hi Pierre,
>
> Thanks very much for your detailed suggestions. It seems
> that in order to
> use CVS, the directory structure of my project must be driven
> by short-term,
> division-of-labor-during-development concerns (Team A, Team B, Shared)
> rather than by the conceptual structure of the classes in my
> project. Too
> bad. I guess I need to learn more about Software
> Configuration Management.
>
To be specific, that is the case if you are determined to use
CVS and no other tools for software configuration management.
If you have been taught that no more than one tool should ever
be necessary, then indeed you need to learn more.
The Unix philosophy is to create tools that do one thing very
well, and to combine those tools as needed. In accordance with
that, CVS does some things very well and some other things not
at all. This is sometimes inconvenient, but such things as
working with the exact specific tools somebody else thought
was exactly what you needed (or what you were going to get,
anyway) can also be inconvenient.
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
