[ 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,
A simple commitinfo script (and related config file) works extremely well
for us
Andy
-Original Message-
From: Heikki Doeleman [mailto:[EMAIL PROTECTED]]
Sent: 30 May 2002 11:55
To: '[EMAIL PROTECTED]'
Subject: Access rights to branches
Some 2 years ago a Shem Mazur asked
Some 2 years ago a
Shem Mazur asked this list about restricting access to particular branches.
There were various replies that didn't seem very conclusive.
For example, I have
a main branch where I allow anyone to check things in, and I have a release
branch where I want to restrict chec
[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 tw
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
On
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?
>
> Wha
"Derek R. Price" wrote:
>
> 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 revisi
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
> *
> 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 pr
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
[EMAIL 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 fr
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
Or train her to use CVS correctly...
- Dennis
- Original Message -
From:
richard offer
To: [EMAIL PROTECTED]
Sent: Monday, October 30, 2000 5:41
PM
Subject: Re: access rights to
branches
* $ from [EMAIL PROTECTED] at "31-Oct:12:31pm" |
* $ 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 wrong branches. Can I restrict her ability to update from
* particular branches or main trunk? The only thing I can find about
* access
Hi,
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? The only thing I can find about
access rights with CVS is to do with Unix file permission this is
fine if you want to
15 matches
Mail list logo
