[Top][All Lists]

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

RE: deprecated caommand in

From: Greg A. Woods
Subject: RE: deprecated caommand in
Date: Wed, 10 Oct 2001 14:12:08 -0400 (EDT)

[ On Wednesday, October 10, 2001 at 09:22:50 (-0400), Stanton, Curt (NCI/IMS) 
wrote: ]
> Subject: RE: deprecated caommand in
>       Well, I am planning on getting comfortable with the concurrent part
> of it, but why not get comfortable with it using CVS seeing as there was
> some sort of locking feature on it already.  I was simply asking if there
> was something like that on the newest version or if I had to start out with
> a previous version.  

There is no traditional check-out locking support in CVS.  Whatever you
think is there is a mostly broken bad idea.  It is deprecated in _because_ it's broken and unworkable.

Either dive right in with CVS, or don't.  If you need some time to get
comfortable with parallel development techniques then practice them with
RCS and read some of the many papers published discussing this
methodology (many tools implement it).

If this is any kind of a problem for you then CVS is probably not going
to meet your requirements and you should stop considering it.

I suspect that if your team needs more orderly interaction with the
versioning tools you use then you should look at something somewhat more
sophisticated than CVS, such as Aegis, as I've already suggested.

                                                        Greg A. Woods

+1 416 218-0098      VE3TCP      <address@hidden>     <address@hidden>
Planix, Inc. <address@hidden>;   Secrets of the Weird <address@hidden>

reply via email to

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