Date: Mon, 19 Aug 2002 14:03:30 -0700 From: "David O'Brien" <obrien@FreeBSD.org> To: Luigi Rizzo <luigi@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/netinet ip_fw2.c src/sbin/ipfw ipfw.8 ipfw2.c Message-ID: <20020819210330.GA4958@dragon.nuxi.com> In-Reply-To: <200208161031.g7GAVmQ7053775@freefall.freebsd.org> References: <200208161031.g7GAVmQ7053775@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 16, 2002 at 03:31:48AM -0700, Luigi Rizzo wrote: > luigi 2002/08/16 03:31:47 PDT > > Modified files: > sys/netinet ip_fw2.c > sbin/ipfw ipfw.8 ipfw2.c > Log: > sys/netinet/ip_fw2.c: > > Implement the M_SKIP_FIREWALL bit in m_flags to avoid loops > for firewall-generated packets (the constant has to go in sys/mbuf.h). Every commit you make to ipfw causes it so that a newer kernel cannot be used with a week old userland (and vice-versa). With the poor shape of -CURRENT this makes it very hard to use -CURRENT as one cannot even test a new kernel for usability before irreversabily updating world. Could you *please* queue up your changes over a longer period of time and hold off any more IPFW commits for a while? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020819210330.GA4958>