info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: access rights to branches


From: Noel L Yap
Subject: Re: access rights to branches
Date: Tue, 31 Oct 2000 08:42:12 -0500

I know this won't address the problem directly.  Anyway, create a commitinfo
script that'll prevent her from checking her stuff into the wrong branch.
Recovery from checking out or updating from the wrong branch should be fairly
straightforward ("cvs up -A").

Noel




address@hidden on 2000.10.30 20:41:29

To:   address@hidden
cc:   (bcc: Noel L Yap)
Subject:  Re: access rights to branches





* $ from address@hidden 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 rights with CVS is to do with Unix file permission.... this is
* fine if you want to stop someone from accessing a project, but not
* enough if you just want to restrict access to a particular branch in the
* project.
*
* Any help much appreciated (she's driving me nuts!!! ;)

Create a .cvsrc file in her home directory with branch tags for update/checkout
?

*
* Shem
*


richard.


-----------------------------------------------------------------------
Richard Offer          Widget FAQ --> http://reality.sgi.com/widgetFAQ/
{X,Motif,Trust} on {Irix,Linux}
__________________________________________http://reality.sgi.com/offer/


_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs





This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]