Date: Fri, 07 Jun 1996 16:40:55 -0700 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: Terry Lambert <terry@lambert.org> Cc: grog@lemis.de, hackers@freebsd.org, freebsd-stable@freebsd.org, FreeBSD-current@freebsd.org Subject: Re: The -stable problem: my view Message-ID: <17086.834190855@time.cdrom.com> In-Reply-To: Your message of "Fri, 07 Jun 1996 11:22:35 PDT." <199606071822.LAA03612@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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). 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. Sorry, CVS is not my favorite utility. Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17086.834190855>