[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Locking support
Noel L Yap
Re: Locking support
Mon, 20 Aug 2001 10:03:37 -0400
Take a look under the project RCVS under SourceForge.
Please note that the "cvs edit -c" patch is for advisory locks. Nothing
prevents a user from circumventing it.
The philosophy is that the advisory locking helps inter-developer communication
without preventing concurrent development. If something has a lock on it, the
would-be editor should find out why it's there and proceed if it's deemed that
the two edits won't conflict (who knows, maybe one of the edits is just for
temporary debug printf's?).
Does anyone know the best way to put locking into CVS?
cvshome has an old patch relative to 1.9 -- is there anything more recent?
If we create a cvsadmin group, this means that cvs admin -l doesn't work.
What should I do? Is there a patch to allow users to do cvs admin -l and -u
(and -k) but not any other cvs admin command? This doesn't seem to difficult
to code, so has anyone done this?
(I am not asking whether to implement locking, only how).
Info-cvs mailing list
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 Chase & Co., its
subsidiaries and affiliates.
- Locking support, Ellison, Martin [IT], 2001/08/19
- Re: Locking support,
Noel L Yap <=
- RE: Locking support, Noel L Yap, 2001/08/21
- RE: Locking support, Ellison, Martin [IT], 2001/08/21
- Re: Locking support, Noel L Yap, 2001/08/21
- RE: Locking support, Noel L Yap, 2001/08/22
- RE: Locking support, Ellison, Martin [IT], 2001/08/22