From owner-cvs-all Tue Oct 29 12: 0:39 2002 Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05CD037B401; Tue, 29 Oct 2002 12:00:38 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4548043E4A; Tue, 29 Oct 2002 12:00:37 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.6/8.12.2) with ESMTP id g9TK0aJR043061; Tue, 29 Oct 2002 12:00:36 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.6/8.12.6/Submit) id g9TJxLJG043037; Tue, 29 Oct 2002 11:59:21 -0800 (PST) Date: Tue, 29 Oct 2002 11:59:21 -0800 From: "David O'Brien" To: Bill Fenner Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/lib/libfetch common.c Message-ID: <20021029195921.GC42760@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org Mail-Followup-To: David O'Brien , Bill Fenner , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org References: <200210291702.JAA05652@windsor.research.att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200210291702.JAA05652@windsor.research.att.com> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Oct 29, 2002 at 09:02:17AM -0800, Bill Fenner wrote: > > > Fix `pkg_add -r' by backing out revs 1.34-1.38. > > No concept of contacting the person who wrote the changes that you > object to and get them to help you debug? Why is FreeBSD's attitude one of all changes are totally justified and if a change breaks something it is up to the one feeling the new breakage to justify any further change? We really need to change our attitude to one that a change that causes a problem is backed out (ie, unbreaks world), and then the change is reviewed to see what went wrong. That leads to better quality software. Instead we allow bugs to enter and sit in the tree while it makes it all the harder to either backout or track down the problem. But do note, I did look for you on IRC to discuss this with you at the time. I can provide a log. But no, I didn't expect you to be on IRC at beckoning to my call at dark-thirty in the morning. > Can I fix my firewall by putting my changes back unilaterally, since > you backed them out unilaterally? Sure. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message