[EMAIL PROTECTED] on 2000.02.23 11:43:38
To: [EMAIL PROTECTED]
cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: CVSROOT/cvsrc
>There is no need to do this. As I've said many times before, communication
>is the key. I'm sure you have manuals or documents of some sort, which tell
>people what proceedures are to be followed. Include the use of CVS among
>them. Put up a developers FAQ/web-page, telling people the most salient
>points they should know...
This is not a communication issue. It's a configuration issue. CVS should have
a way to set default configurations (at least per repo or possibly per module).
Your view seems to say that there should be no such thing as /etc/profile for sh
and that users must create there own .profile files.
Furthermore, developers already have to learn a lot in an environment. The less
they have to know, the better they can know the rest. This means that, if
CVSROOT/cvsrc existed, CVS procedures and default behaviours can be documented,
but users won't have to create their own .cvsrc (unless they wish to extend or
override the defaults).
Noel
