From owner-freebsd-current  Wed May 21 09:20:59 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id JAA18664
          for current-outgoing; Wed, 21 May 1997 09:20:59 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA18652
          for <current@FreeBSD.ORG>; Wed, 21 May 1997 09:20:55 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id CAA31817; Thu, 22 May 1997 02:16:07 +1000
Date: Thu, 22 May 1997 02:16:07 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199705211616.CAA31817@godzilla.zeta.org.au>
To: bde@zeta.org.au, jkh@time.cdrom.com
Subject: Re: IPDIVERT broken?
Cc: asami@vader.cs.berkeley.edu, current@FreeBSD.ORG, jdp@polstra.com,
        rob@ideal.net.au
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>> I agree with this out of context quote.  Developers should repair the
>> results of any interface changes to their code.  Changers shouldn't be
>> expected to do it all.
>
>Eh?  So you're saying that you think that it's valid practice to do a
>drive-by shooting on /usr/src and then expect the developers to pick
>up the pieces?

Developers should help make the changes.  For ipdivert and nonstandard
network protocols they were given several weeks notice but apparently
didn't do anything until after the changes were committed.

Bruce