atom feed75 messages in org.freebsd.freebsd-hackersRe: The -stable problem: my view
FromSent OnAttachments
Greg LeheyJun 7, 1996 3:15 am 
Jordan K. HubbardJun 7, 1996 6:29 am 
Nate WilliamsJun 7, 1996 8:29 am 
Karl Denninger, MCSNetJun 7, 1996 8:41 am 
Nate WilliamsJun 7, 1996 10:02 am 
Terry LambertJun 7, 1996 11:22 am 
Angelo TurettaJun 7, 1996 11:48 am 
Marc G. FournierJun 7, 1996 12:05 pm 
Nate WilliamsJun 7, 1996 12:53 pm 
Terry LambertJun 7, 1996 12:53 pm 
Nate WilliamsJun 7, 1996 1:07 pm 
Terry LambertJun 7, 1996 2:12 pm 
Nate WilliamsJun 7, 1996 2:26 pm 
Terry LambertJun 7, 1996 2:58 pm 
Nate WilliamsJun 7, 1996 3:07 pm 
Terry LambertJun 7, 1996 3:15 pm 
Nate WilliamsJun 7, 1996 3:24 pm 
Jordan K. HubbardJun 7, 1996 4:00 pm 
Nate WilliamsJun 7, 1996 4:06 pm 
Jordan K. HubbardJun 7, 1996 4:27 pm 
Jordan K. HubbardJun 7, 1996 4:40 pm 
Terry LambertJun 7, 1996 4:42 pm 
Jordan K. HubbardJun 7, 1996 4:56 pm 
Justin T. GibbsJun 7, 1996 5:35 pm 
Jordan K. HubbardJun 7, 1996 5:59 pm 
Jordan K. HubbardJun 7, 1996 6:07 pm 
Nate WilliamsJun 7, 1996 6:13 pm 
Scott BlachowiczJun 7, 1996 7:03 pm 
Michael HancockJun 7, 1996 7:08 pm 
Nate WilliamsJun 7, 1996 7:21 pm 
Michael HancockJun 7, 1996 7:25 pm 
Michael HancockJun 7, 1996 7:30 pm 
David GreenmanJun 7, 1996 9:06 pm 
Nate WilliamsJun 7, 1996 9:07 pm 
Terry LambertJun 7, 1996 9:10 pm 
Nate WilliamsJun 7, 1996 9:18 pm 
Terry LambertJun 7, 1996 9:39 pm 
Terry LambertJun 7, 1996 9:58 pm 
Jordan K. HubbardJun 7, 1996 10:13 pm 
Jordan K. HubbardJun 7, 1996 10:24 pm 
Terry LambertJun 7, 1996 10:24 pm 
Nate WilliamsJun 7, 1996 10:26 pm 
Jordan K. HubbardJun 7, 1996 10:33 pm 
Nate WilliamsJun 7, 1996 10:34 pm 
David GreenmanJun 7, 1996 10:40 pm 
Terry LambertJun 7, 1996 11:03 pm 
John BirrellJun 7, 1996 11:18 pm 
Justin T. GibbsJun 7, 1996 11:22 pm 
Rodney W. GrimesJun 8, 1996 1:24 am 
Jordan K. HubbardJun 8, 1996 2:28 am 
NarviJun 8, 1996 2:33 am 
NarviJun 8, 1996 2:53 am 
NarviJun 8, 1996 3:05 am 
Heiko BlumeJun 8, 1996 4:29 am 
Michael HancockJun 8, 1996 8:22 am 
Garrett WollmanJun 8, 1996 11:18 am 
Justin T. GibbsJun 8, 1996 1:52 pm 
M.R.MurphyJun 8, 1996 2:10 pm 
Terry LambertJun 8, 1996 2:52 pm 
M.R.MurphyJun 8, 1996 3:40 pm 
Jordan K. HubbardJun 8, 1996 4:08 pm 
Julian H. StaceyJun 9, 1996 3:54 am 
Randy TerbushJun 9, 1996 7:21 am 
Bob WillcoxJun 9, 1996 7:54 am 
Chuck RobeyJun 9, 1996 8:34 am 
Randy TerbushJun 9, 1996 8:40 am 
Ollivier RobertJun 9, 1996 12:56 pm 
Bob WillcoxJun 9, 1996 2:32 pm 
Andrew V. StesinJun 10, 1996 1:45 am 
NarviJun 10, 1996 6:54 am 
Andrew V. StesinJun 10, 1996 7:40 am 
NarviJun 10, 1996 8:48 am 
Michael RobinsonJun 14, 1996 2:38 am 
Amancio HastyJun 14, 1996 3:00 am 
Terry LambertJun 17, 1996 11:32 am 
Subject:Re: The -stable problem: my view
From:Terry Lambert (ter@lambert.org)
Date:Jun 7, 1996 4:42:34 pm
List:org.freebsd.freebsd-hackers

The problem with CVS is access protocol. I've suggested (many times) that the way to resolve this is to establish reader/writer locks and a shell script interface for use by committers or other programs, and

Oh, did I also forget to mention that CVS's locking code is totally bogus and slow? :-)

It takes *two hours* to check out a copy of /usr/src, not to mention all the time wasted in locking down the tree during commits (CVS crawls through the area you're committing and slaps down lock files everywhere, very very slowly).

Gee, if only you had top level reader/writer locks so you could turn off the per file locking if a global lock was present and spend about 16,000 less lock/unlock calls. 8-).

Then there's the wonderful feeling when you've done a whole set of cleanups to /usr/src and have to do a "commit from the top" - you wait 45 minutes for it to crawl its way through, only to be informed at the end that somebody changed a file in some _completely unrelated_ section of the tree and now, rather than simply merging it in for you (e.g. this is NOT a conflict situation!) CVS aborts and says "I can't go on!". You need to update in the change then start your commit all over again.

Gee, if only you had top level reader/writeer locks that were multiple reader/single writer to serialize groups of changes over a set of 'n' files. 8-).

Sorry, CVS is not my favorite utility.

The problem isn't CVS, it's what you put on top of it. You might as well blame RCS for you CVS problems as CVS for your protocol/policy enforcement problems. 8-).