From owner-freebsd-current Wed May 21 08:18:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA15834 for current-outgoing; Wed, 21 May 1997 08:18:52 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA15825 for ; Wed, 21 May 1997 08:18:49 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id IAA16848; Wed, 21 May 1997 08:18:44 -0700 (PDT) Message-Id: <199705211518.IAA16848@austin.polstra.com> To: "Jordan K. Hubbard" cc: current@FreeBSD.ORG Subject: Re: IPDIVERT broken? In-reply-to: Your message of "Tue, 20 May 1997 22:22:52 PDT." <18183.864192172@time.cdrom.com> References: <18183.864192172@time.cdrom.com> Date: Wed, 21 May 1997 08:18:44 -0700 From: John Polstra Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Yes, it was broken on April 27 by Garrett's "long-awaited > > mega-massive-network-code-cleanup. Part I." Do a "cvs log > > src/sys/sys/socketvar.h" for the gory details. > > Am I alone in thinking that changes which break other things in the > source tree should be fixed by the changer? No, you're not alone. I feel exactly the same way. If you don't have time to fix all the breakage caused by a change, then you don't have any business making the change at all. This is doubly true when it's other people's code that you're breaking. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth