Julien [EMAIL PROTECTED] writes:
when I use the "cvs [EMAIL PROTECTED]:/cvsroot/myrepository co
.", The server send me the emptied directories I just talk about
previously. Sure I can make a "cvs update -P" to get rid off this dirs.
Use the "-P" flag with the co, like in "cvs co -P .".
It is not quite true that WinCVS is GPL'ed. WinCVS uses the
CodeJock MFC
library (www.codejock.com), which is NOT GPL. Below is a
portion of the
CodeJock license (http://www.codejock.com/terms_of_use.htm):
...
If you do not meet the requirements for free use of the
SOFTWARE, you may
1) write a script which fixes all the refs to the old
repository in the
Repository files (plus fix their CVSROOT)?
That usually turns out to be the best way.
Yes, at least when moving to a similar disk (ext2 to ext2 eg). I moved from
an NT to a linux (NTFS to ext2) and noticed that
However, I agree with Noel about minimizing sysadmin involvement.
Sysadmin should only be required to set up user accounts.
The setup of the CVS project, repository, management of permissions,
etc., none of it should require sysadmin involvement.
This is one of the biggest reasons I am
CVS using a non-socket/port transport like rsh or ssh
to connect to a server machine. "cvs server"
As secure as the transport.
E.g. requires account administration on the
machine on which cvs server will run.
You lose very much in performance if you run cvs "locally"
?!?!
Regards, EOF
-Original Message-
From: Fredrik Liljegren [mailto:[EMAIL PROTECTED]]
Sent: 03 May 2000 11:30
To: '[EMAIL PROTECTED]'
Subject: Read-only local (ssh) access
How do I manage to give a certain user a read-only access only for the
cvs-repository?
When I set up
