[Top][All Lists]

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

RE: deprecated caommand in

From: Thornley, David
Subject: RE: deprecated caommand in
Date: Tue, 9 Oct 2001 16:55:37 -0500

> -----Original Message-----
> From: Stanton, Curt (NCI/IMS) [mailto:address@hidden
> Sent: Tuesday, October 09, 2001 2:32 PM
> To: 'address@hidden'
> Subject: RE: deprecated caommand in
> First of all relax.  Second of all, I like a lot of things 
> about CVS.  We
> would like to try to avoid problems right away by trying this 
> way, which was
> already there in previous versions, until we are comfortable 
> without it.  I
> was merely asking if there was a way to do it in the latest 
> release, not
> asking anyone to spend time on something that the software 
> isn't working
> towards
You could always look at the "cvs watch"/"cvs edit" facility,
which exists to let people know who is working on what files.
In my experience, communication is a completely adequate substitute
for hard locks.  If this is not the case in your shop, you have
problems that no software is going to solve.

This has the advantage that two people will sometime wind up
working on the same thing, and will find out about it, and so they
may well try the CVS merge facilities and get comfortable with it.

I think that concurrent development, when it works, is a Very
Good Thing.  The problem with using CVS in concurrent-only mode
is that it's a matter of preaching to the choir, as only people
already sold on concurrent development are going to use it.

reply via email to

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