[Top][All Lists]

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

Re: reserved checkout

From: Noel Yap
Subject: Re: reserved checkout
Date: Thu, 31 Jan 2002 06:17:04 -0800 (PST)

You tried forcing serial development into a tool meant
for concurrent development :-)

Seriously, though, I (and I think most others) see
that there is absolutely no reason to _prevent_
concurrent development although I think it should
sometimes be /avoided/.

The way to avoid it is through communication.  There
are patches available at SourceForge under project
RCVS that'll extend the "cvs edit" command to help
with communication.  Take a look at them.

--- Matthias Kienle
<address@hidden> wrote:
> Hello,
> I am a beginner with reserved checkout. I found
> several helpentries on
> the cvshome page and want test a method using the
> rcslock file. I added
> a line in the commitinfo file like the follow:
> ALL /usr/lib/cvs/contrib/rcslock
> If user A locks and edit a file out of the
> repository subsequently an
> other user edit the file. User B commit first the
> file and should
> receive an error but the commit ends successfully. I
> activated strict
> locking for the cvs repository.
> What do I wrong?
> Matthias
> _______________________________________________
> Info-cvs mailing list
> address@hidden

Do You Yahoo!?
Great stuff seeking new owners in Yahoo! Auctions!

reply via email to

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