[EMAIL PROTECTED] on 2000.02.23 10:48:50
>On Wednesday, February 23, "Noel L Yap" wrote:
>> There's currently no global .cvsrc. There's been discussion about it, but
>> AFAIK, noone has begun any work on it. Personally, I would find it useful,
but
>> we work around the issue using symlinks and copies (the global .cvsrc doesn't
>> change much anyway).
>
>This sort of thing (to me at least) is indicative of a group of people who
>do not understand CVS, do not understand how it works, and are being spoon-
>fed in order for them to be able to work with CVS. The type of people that
>I tend to refer to as wintel-weenies.
>
>While a global configuration method may well be a good thing for CVS, I'm
>still hoping that the world will become a better place, people will try to
>understand the tools they use, and in general will not be scared to actually
>read a manual, or a web page, that describes the possibility of having their
>own .cvsrc file.
>
>Then again, I would not be surprised if the same people are the ones that
>think they need locking, when they do not. In some sense, a cheap parting
>shot, but before you answer and flame away, take a minute, and think about
>what I just said...
Perhaps generally. In our case, though, we have some extremely bright people
whose background does not include CM (they do, however, include computational
finance (ie business-related stuff)). All they have to do is use the tool the
way an admin (ie policy-maker) says it should be used. Your comment is akin to
saying that, to fill up a gas tank, one needs to know the internals of the
combustion engine.
To give them some credit, they have seen the light of concurrent development.
Noel
