[EMAIL PROTECTED] on 2000.02.24 16:18:19
>On Thursday, February 24, "Noel L Yap" wrote:
>> >
>> >My point is that, for someone who works with multiple repositories,
>> >changing from one directory to another could change repositories and it
>> >would be very surprising for CVS commands to suddenly change their
>> >behavior just because of changing directories.
>>
>> Yes, this is true. I'd say, though, that this feature shouldn't be used in
>> these environments, CVSROOT/cvsrc should be consistent among the various
>> repositories, or the user should override the repository default settings.
>
>Some of us do not have any control (other than commit/checkout type) over
>the multiple repos that we are using... so this is not an option. Also,
>"overriding" stuff locally (which is what would need to happen) now becomes
>the same as having a "default" configuration set within the CVS binary (as
>it stands now), and doing the ~/.cvsrc to change that. In other words,
>a lot of people have gained nothing, in fact they now need to maintain their
>own ~/.cvsrc file to simply gain *CONSISTENCY*, not good, IMHO...
Wow, you guys really feel strongly about this.
I'll just say that repositories open to those who have no say as to what should
go into CVSROOT/cvsrc shouldn't put anything in it (just as repositories open to
read-only clients shouldn't have CVSROOT/history (unless I misunderstand
something about CVSROOT/history)).
Now, since I don't feel as strongly regarding my opinion, I'll just drop the
subject. If anyone else shares my opinion (that CVSROOT/cvsrc is a good idea),
it's up to you to pick up where I left off.
Noel
