Date: Tue, 13 Jan 1998 12:10:13 -0800 (PST) From: Simon Shapiro <shimon@simon-shapiro.org> To: Julian Elischer <julian@whistle.com> Cc: current@freebsd.org Subject: Re: Firewall in kernel? - Found it! Message-ID: <XFMail.980113121013.shimon@simon-shapiro.org> In-Reply-To: <Pine.BSF.3.95.980112002449.15549E-100000@current1.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12-Jan-98 Julian Elischer wrote: ... > Yes but it would slow down my own verification of the correctness of my > patches.. My method is: > edit/build/test/edit/build/test > make world (not always fora a smaller commit) > cvs diff > apply diff to my commit tree > commit (remotly) > cvsup to local cvs tree <-------XXX > checkout entire sources > make kernel(s) > make world > this way I catch any stuffups As usual, replacing accountability with procedure is costly. The cycle you describe is accountability. If everyone will always do that, there will be no need for procedure. You use the term ``not always'', which implies deviation. Small changes may cause big headaches. It is a compromise, and I hear the concensus is that it is a good one. I will agree that the technology and procedure we use are the best I have seen. Maybe improvement in procedure are of diminishing return. PErsonally, this last incident was an easy one to overcome, as the bugs were obvious. I also did not hear anyone moaning too loudly. Just specifying ``did that happened to you too?'' I need to think about this one some more. Maybe the process IS good enough. > It aint purfect, but it's remarkable how effective it is. > this last week has been an aberation rather than the norm. I tend to agree. > (ps. new devfs code out..) Great! ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.980113121013.shimon>