From owner-freebsd-stable  Sat Jun 29 18:56:32 1996
Return-Path: owner-stable
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA17706
          for stable-outgoing; Sat, 29 Jun 1996 11:03:37 -0700 (PDT)
Received: from zen.nash.org (nash.pr.mcs.net [204.95.47.72])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA17663
          for <stable@freebsd.org>; Sat, 29 Jun 1996 11:03:01 -0700 (PDT)
Received: (from alex@localhost) by zen.nash.org (8.7.5/8.6.12) id NAA06732; Sat, 29 Jun 1996 13:03:17 -0500 (CDT)
Date: Sat, 29 Jun 1996 13:03:17 -0500 (CDT)
Message-Id: <199606291803.NAA06732@zen.nash.org>
From: Alex Nash <alex@zen.nash.org>
To: nox@jelal.hb.north.de
Cc: stable@FreeBSD.ORG
Subject: Re: ipfw (was: Re: lockups.)
Reply-to: nash@mcs.com
Sender: owner-stable@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > You mean -stable.  Yes, as of Monday this week, -current and -stable
> > are in sync.
> 
> Actually i was talking about the (date of the) struct ip_fw change,
> but nevermind.

*sigh*  How difficult is this?  One last time:

Look at the CVS logs for ip_fw.h again.  -current is at rev 1.20, dated
June 9th, this was when the ipfw struct changes took place.  -stable
is at rev 1.11.4.7, dated June 25 (it was Monday here when I committed
it), this is when the struct changes from -current were incorporated
into -stable.

Alex