-Original Message-
From: Larry Jones [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 02, 2005 1:34 PM
To: Fouts Christopher (IFNA MP DC)
Cc: info-cvs@gnu.org
Subject: Re: user privileges for files / dirs / modules
[EMAIL PROTECTED] writes:
Thanks, but I believe I've done
[EMAIL PROTECTED] writes:
I'm not trying to do anything special. Just for some reason, if I
co/ci a file in my .../CVSROOT dir, other files perms get reset,
e.g., logtags and taglogs.
That's because whenever you check in something in $CVSROOT/CVSROOT,
*all* of the administrative files get
Larry Jones wrote:
[EMAIL PROTECTED] writes:
I'm not trying to do anything special. Just for some reason, if I
co/ci a file in my .../CVSROOT dir, other files perms get reset,
e.g., logtags and taglogs.
That's because whenever you check in something in $CVSROOT/CVSROOT,
*all* of the
[EMAIL PROTECTED] wrote:
I'm hoping this is as simple as this. Though for some reason,
my $CVSROOT/CVSROOT files get reset whenever I submit something
in there, then I have to manually chmod. I have a taglogs and
a logtags file that change to r--r--r--. The logtags file is just
a script that
-Original Message-
From: Jim.Hyslop [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 02, 2005 9:37 AM
To: Fouts Christopher (IFNA MP DC); info-cvs@gnu.org
Subject: RE: user privileges for files / dirs / modules
[EMAIL PROTECTED] wrote:
I'm hoping this is as simple as this. Though
[EMAIL PROTECTED] writes:
Yes I started the discussion back then too, and did not get
(or I couldn't filter out) a straight answer. So once checked-in
with the wrong perms, how does one correct it?
By changing the permissions on the RCS file in the repository. The
permissions on the working
-Original Message-
From: Larry Jones [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 02, 2005 12:15 PM
To: Fouts Christopher (IFNA MP DC)
Cc: info-cvs@gnu.org
Subject: Re: user privileges for files / dirs / modules
[EMAIL PROTECTED] writes:
Yes I started the discussion back
[EMAIL PROTECTED] writes:
Thanks, but I believe I've done this, that is, changing the RCS
file perms to no avail. Now I remember asking where in the RCS
file, and getting not in the RCS file, but of the RCS file.
Correct, it's the permissions of the RCS file itself that are used.
What
[EMAIL PROTECTED] wrote:
-Original Message-
From: Larry Jones [mailto:[EMAIL PROTECTED]
[EMAIL PROTECTED] writes:
Yes I started the discussion back then too, and did not get (or I
couldn't filter out) a straight answer. So once checked-in with the
wrong perms, how does one
Is it possible to give specific files / directories / modules specific user
privileges? We need to be able to give people access priviledges to selective
directories. Normally, one has access only to the component that he is working
on.
Our CVS repository (/cvs) is stored on a RedHat 9 machine. A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
Is it possible to give specific files / directories / modules specific
user privileges? We need to be able to give people access priviledges
to selective directories. Normally, one has access only to the
component that
[EMAIL PROTECTED] wrote:
Is it possible to give specific files / directories / modules
specific user privileges?
[...]
Our CVS repository (/cvs) is stored on a RedHat 9 machine. A
group 'cvsusers' exists.
Typically for this scenario, it's as simple as taking advantage of the
security
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
] On Behalf Of Jim.Hyslop
Sent: Tuesday, February 01, 2005 2:57 PM
To: '[EMAIL PROTECTED]'; info-cvs@gnu.org
Subject: RE: user privileges for files / dirs / modules
[EMAIL PROTECTED] wrote:
Is it possible to give
[EMAIL PROTECTED] writes:
Is it possible to give specific files / directories / modules specific user
privileges?
Yes, on a per-directory basis. See the manual for details:
https://www.cvshome.org/docs/manual/cvs-1.11.18/cvs_2.html#SEC13
-Larry Jones
From now on, I'm devoting
14 matches
Mail list logo
