[ On Thursday, May 30, 2002 at 12:55:21 (+0200), Heikki Doeleman wrote: ]
Subject: Access rights to branches
Can anyone tell me what is, these days, the most straightforward solution to
this issue ? You'd say that something like this is wanted in many
organizations, there must surely be an
When might the patch referred to below make it into a future CVS
release? Thanks
Chuck Irvine
Sprint
-Original Message-
From: chris.cameron [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 31, 2000 1:58 PM
To: ljnelson; smazur
Cc: info-cvs
Subject: RE: access rights to branches
[EMAIL PROTECTED] wrote:
When might the patch referred to below make it into a future CVS
release?
Probably about the same time that the cvs edit -c patch does. :-(
Cheers,
Laird
--
W: [EMAIL PROTECTED] / P: [EMAIL PROTECTED]
http://www.amherst.edu/~ljnelson/
Good, cheap, fast: pick two.
Shem Mazur wrote:
I have a CVS user who continues to checkout modules or update files from
the wrong branches. Can I restrict her ability to update from
particular branches or main trunk?
What the various other replies were trying (somewhat unhelpfully :-)) to
tell you is no, not with CVS
PROTECTED] on 2000.10.30 20:41:29
To: [EMAIL PROTECTED]
cc: (bcc: Noel L Yap)
Subject: Re: access rights to branches
* $ from [EMAIL PROTECTED] at "31-Oct:12:31pm" | sed "1,$s/^/* /"
*
*
* Hi,
*
* I have a CVS user who continues to checkout modules or update files from
* the w
Laird Nelson wrote:
That said, if you know that your user will never try to force a commit
using the -r switch (don't know how you'd know this, but most users
don't use this flag), then you can write a commitinfo script that will
check the old revision number and reject access based on it,
Can I restrict her ability to update from
particular branches or main trunk?
We have a similar issue in that we need to restrict who can update which
files on the mainline and (sometimes branches). There was some discussion of
this recently and the general approach taken was to implement a
Andrew Gilmartin wrote:
What would be useful to us is a pre-commit check that made sure the user can
revise a given file and given branch or mainline. For example,
# user file development-line
* #none #none
*
On Wednesday, November 01, 2000 1:43 AM, Laird Nelson
[SMTP:[EMAIL PROTECTED]] wrote:
Shem Mazur wrote:
I have a CVS user who continues to checkout modules or update files
from
the wrong branches. Can I restrict her ability to update from
particular branches or main trunk?
What the
