[Top][All Lists]

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

RE: Locking support

From: Greg A. Woods
Subject: RE: Locking support
Date: Wed, 22 Aug 2001 13:17:14 -0400 (EDT)

[ On Wednesday, August 22, 2001 at 10:11:47 (-0400), Noel L Yap wrote: ]
> Subject: RE: Locking support
> If it weren't for the fact that they had to abandon PVCS, they would not have
> adopted concurrent development.

I can understand that....

> There's no better education than experience.  These patches give developers a
> chance to be eased into concurrent development.  The only backfire I can think
> of is if a user didn't adhere to team practices and procedures.  If the team
> never stops using the patches, so what?  Concurrent development can still
> happen, but it's just a little more controlled.

And there's no better way to get experience than to jump in head first.

Of course you might ask someone already in the water if it's deep enough
for you to dive in, but they did, and you gave them a truthful answer.
If they were afraid they couldn't do a shallow dive then they should
have just gone for a belly flop and hoped the pain would be over soon.
(After all they weren't getting back off the diving board with that
bully standing back there telling them to jump or be pushed!  ;-)

You sure as heck don't usually go diving, even just off the edge of the
pool with crutches under your arms....

(Now the "cvs edit" stuff (patched or not) isn't a crutch if it's being
used as *the* primary developer intercommunications tool, but I'm not
sure it's suitable for that, so I still don't really see much point in
supporting it.)

                                                        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]