[Top][All Lists]

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

Re: CVS - setup reserved checkout

From: yap_noel
Subject: Re: CVS - setup reserved checkout
Date: Tue, 30 Oct 2001 09:31:40 -0500

>address@hidden (Kaz Kylheku) wrote:
>>Tell the manager to shed his or her superstitions, and work with
>>the facts. The facts are:
>>- Concurrent development works just fine.
>>- Your team already likes it.
>>- Strict locking does not prevent concurrency, it only reduces
>>  it to a coarse granularity: coarse enough to interfere with
>>  productivity, but not coarse enough to eradicate conflicts.
>>  To eliminate conflicts, you have to lock the entire repository
>>  so that only one developer at a time can do anything on the
>>  software base as a whole.
>Well said.  May I add, Concurrency works best with good communication
among the
>developers.  Responsibility of certain sections of code is usually divvied
>just a few people.  Strict locking might hurt the need for good
>among a group.

Yes, exactly.  The advisory locks patch (that I so eagerly advertise) is
meant to increase communication among the developers, not to create true
reserved locks (as the patch name implies -- I need to change this name).


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.

reply via email to

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