Date: Sat, 21 Feb 1998 11:09:12 -0700 From: Nate Williams <nate@mt.sri.com> To: Terry Lambert <tlambert@primenet.com> Cc: sef@kithrup.com (Sean Eric Fagan), current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. Message-ID: <199802211809.LAA20161@mt.sri.com> In-Reply-To: <199802210342.UAA13837@usr04.primenet.com> References: <199802210306.TAA07907@kithrup.com> <199802210342.UAA13837@usr04.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[ Broken -current builds ] > The same thing happened at Novell, until we instituted multiple > reader, single writer locking in a trivial front-end to cvs, and > started slapping people who didn't build test affected code before > releasing the writer lock. The same thing happenned at my work, until we let live llama loose in the office. Then, if someone made a bad commit, we publically chastised them and told them never to do it again, but I think the *real* reason was because of the llamas, and not the chasting of the people. I'm sure the reader/writer locks also were why things worked at Novell, and not the slapping around. (ps. In case you missed, that was sarcasm, playing on the totally non-sequiter answer Terry gave.) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802211809.LAA20161>