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 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 various other replies were trying (somewhat unhelpfully :-))
to
> tell you is no, not with CVS out of the box. With its commitinfo
> mechanism you can't get access to either (a) the new revision number
> prior to the commit taking place (a feature that sure would be nice to
> have) or (b) whether or not the user supplied a -r switch to the
commit
> command. If you could get either (a) or (b) then you could reliably
> block commits onto a branch.
>
There was a patch posted to this group a while ago, to add revision
information to the rest of the information passed to commitinfo. Check
out
the following at cvshome.org for more details:
http://www.cvshome.org/cyclic/cvs/dev-commitinfo.txt
http://www.cvshome.org/dev/patches/commitinfo
These both seem to be pointers to the same patch, but I haven't
confirmed
this. This patch will require changes to all your commitinfo scripts.
***************************************************************
Chris Cameron Open Telecommunications NZ Ltd
Senior Solution Architect IN Product Management
[EMAIL PROTECTED] P.O.Box 10-388
+64 4 495 8403 (DDI) The Terrace
fax: +64 4 495 8419 Wellington
cell: +64 21 650 680 New Zealand
Life, don't talk to me about life ....(Marvin - HHGTTG)
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs