Hello,
We are using Cvs for Unix Repositories and both Unix
and Windows clients.
I am using a script through commitinfo to restrict
user access to different modules located under the
same $CVSROOT.
The script reads from a text file containing a list of
repositories along with users who can
--- Nate Swenson [EMAIL PROTECTED] wrote:
Are you running a patched version on both the
client
and the server?
The patched version of cvs is running on a linux
server.
The client is running WinCvs on a Win2000
workstation.
I think this is the root of your problem. The
client
I am running a patched version of cvs on a linux server and the clients are
running WinCvs on Win2000 workstations. The -c options that should be
available through the patch are not working in WinCvs and the root of my
problem seems to be that I haven't applied the patch to WinCvs. Does anyone
Rob Helmer wrote:
If you must run on Windows 2000, try CygWin : http://www.cygwin.com
It comes with cvs and a bunch of other Unix tools compiled for
Windows.
Note that using Cygwin for Windows CVS can cause great headaches unless you
pay
constant attention to line terminators.
Hi all,
I have some shell scripts that are executed from the working directory
of one of the users in our system (Call it 'user X'). The problem I am
having is that, if the scripts are modified and user X updates, the
execute permissions are gone.
CVSREAD is set, but I thought it would only
--- James Hughes [EMAIL PROTECTED] wrote:
I have some shell scripts that are executed from the
working directory
of one of the users in our system (Call it 'user
X'). The problem I am
having is that, if the scripts are modified and user
X updates, the
execute permissions are gone.
When running `cvs log` on the file Image55.jpg, I get the following output:
cvs log Image55.jpg (in directory C:\dssi\cameras\cam1\tools\doc\WinCVS\)
cvs log: warning: duplicate key `þ|-Á¿Ã¯Ãÿ' in RCS file
`E:\CVSROOT/cameras/cam1/tools/doc/WinCVS/Image55.jpg,v'
cvs log: warning:
