Hi!
On Tue, Jun 05, 2001 at 04:14:19PM -0400, Larry Jones wrote:
> > So, the problem is, that any file, locked by any ordinary user, may be
> > unlocked by any - same or other - user, and then locked again with his own
> > lock. There is an error message when an other user wants to lock an already
> > locked file, or unlocks a file that is not locked. But, when wanting to
> > unlock a file locked by anyone, it gets unlocked immediately, without any
> > warning or error.
>
> Note that that only happens if you specify a particular revision to
> unlock; if you just use -u with no revision, you get a message telling
> you that you don't have the file locked. In this situation, RCS would
No. That's the point. As a user, I may issue a:
cvs admin -u <file>
and it gets unlocked. That's the thing I don't understand.
> tell you that the file is locked by someone else and ask you if you want
> to break the lock or not. Unfortunately, that is not compatible with
> CVS's client/server operation since only the server knows about locks
> and only the client is able to communicate with the user.
But it sounds a little bit hazardous, since you aquire a lock on a file in
the repository, and it requires a server operation. The client is only an
intermediate partner between you and the server, IMHO.
Thanks for the prompt help :)
Laszlo
--
Murvai-Buzogány László [EMAIL PROTECTED]
_______________________________________________
Bug-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-cvs
