Julian Opificius wrote:
>
> Todd Denniston wrote:
> >
> > Big question: What do you think using :pserver: at this point, gain you and
> > your users over just :ext: over ssh?
> >
> > Because they already have (and will continue to have) valid system shell
> > login, from here it only looks like mo
Hi
I'm reading the manual for CVS 1.11.20 and on page 27 (preprinted on the
page, however, the .pdf document shows it to be page 29) I find the
documentation for readers and writers files somewhat confusing and
ambiguous. Could both readers and writers coexist or one at any given time?
Que
I've set up a CVS module with "cvs watch on" so that users have to use
"cvs edit" to reserve files for editing. This works fine for serial
editing of unmergeable binary files files. When users try to edit
files already marked for editing by someone else they are told the file
is unavailable for e
Todd Denniston wrote:
Big question: What do you think using :pserver: at this point, gain you and
your users over just :ext: over ssh?
Because they already have (and will continue to have) valid system shell
login, from here it only looks like more admin trouble to setup and maintain
pserver,
Julian Opificius wrote:
>
> Thanks for this input!
>
> The problem is that each of these articles achieve their intended
> results by restricting commands to "cvs". I don't want to do that: my
> CVS users are my engineering department members with legitimate logins.
> It's only access to the CVS
