From owner-freebsd-current Thu Jun 6 2:39:19 2002 Delivered-To: freebsd-current@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 46A6C37B404 for ; Thu, 6 Jun 2002 02:39:14 -0700 (PDT) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.36 #1) id 17Ftjm-0000dg-00; Thu, 06 Jun 2002 11:39:22 +0200 From: Sheldon Hearn To: Scott Long Cc: Dag-Erling Smorgrav , Michael Nottebrock , freebsd-current Subject: Re: buildworld failure in libfetch In-reply-to: Your message of "Wed, 05 Jun 2002 16:44:55 CST." <20020605224455.GA14866@hollin.btc.adaptec.com> Date: Thu, 06 Jun 2002 11:39:22 +0200 Message-ID: <2459.1023356362@axl.seasidesoftware.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 05 Jun 2002 16:44:55 CST, Scott Long wrote: > Ok, I finally feel the need to speak up here. > > DES, > > FREEFALL CVS IS NOT THE PLACE TO PUT EXPERIMENTAL CODE THAT BREAKS WORLD! > PERIOD! > > Don't give me any crap about "It's -current, you should expect breakage." > You are abusing this disclaimer far more than it was ever meant for. > Breaking world used to be a very humiliating event for committers. You, > however, break it on a consistent basis. What the F*CK? Yes, others > have broken world before you, and others will break it after you, but > you are abusing the standards of the project. I think you went a little over the top with this message. If you'd taken a moment to calm down and limited yourself to presenting an emotion-free complaint, you'd be in a much better position to expect a positive result. Yes, DES broke the world build. Yes, more / better testing on his part could have avoided the breakage. Still, it's seldom useful to come on so strong. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message