Hello, Tobias!
> 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.
But if everybody works on the same project, why should they maintain
separate .cvsrc ?
IMO personal configuration files are needed only for those who have
personal preferences. People who have no preferences should use defaults.
But the defaults may be different for different sites/repositories.
> Then again, I would not be surprised if the same people are the ones
> that think they need locking, when they do not.
Exactly! But I want to make CVS work better for them. Especially
forgetting "-d" after "cvs update" is a major hassle because they cannot
compile the project, then they run "su" and grab the code from my home
directory (or even compile it there!), and then they complain that my code
doesn't work for them.
I really want to stop accessing each others' directories, that's why I
don't want to mess with "forced distribution" of .cvsrc
Pavel
