[Top][All Lists]

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

RE: deprecated caommand in

From: Stanton, Curt (NCI/IMS)
Subject: RE: deprecated caommand in
Date: Wed, 10 Oct 2001 09:22:50 -0400

        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.  

> [ On Tuesday, October 9, 2001 at 15:31:46 (-0400), Stanton, Curt (NCI/IMS)
> wrote: ]
> > 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
> It really doesn't matter how much you like some features of CVS if you
> don't like the "concurrent" part -- CVS was designed to force its users
> into the concurrent (parallel) development model.  If you don't want to
> do that then you do not want to use CVS.
> Conversely If you really really really want to use CVS then you really
> really really must get comfortable with the concurrent development
> model.
> You might also want to look at other tools which allow concurrent
> development but with a more controlled two-phase commit mechanism,
> eg. Aegis.
> -- 
>                                                       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]