From owner-freebsd-current@FreeBSD.ORG Thu Mar 30 08:44:14 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9455216A401 for ; Thu, 30 Mar 2006 08:44:14 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B9B843D4C for ; Thu, 30 Mar 2006 08:44:14 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id C676F46BAF; Thu, 30 Mar 2006 03:44:13 -0500 (EST) Date: Thu, 30 Mar 2006 08:44:13 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Peter Jeremy In-Reply-To: <20060330084050.GC736@turion.vk2pj.dyndns.org> Message-ID: <20060330084257.I9972@fledge.watson.org> References: <20060317141627.W2181@fledge.watson.org> <20060329100839.V19236@fledge.watson.org> <20060330084050.GC736@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@freebsd.org Subject: Re: REMINDER: Re: HEADS UP: network stack and socket hackery over the next few weeks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Mar 2006 08:44:14 -0000 On Thu, 30 Mar 2006, Peter Jeremy wrote: > On Wed, 2006-Mar-29 10:11:57 +0000, Robert Watson wrote: >> As a reminder, April 1 is now three days away. On April 1, I will be >> committed an extensive set of socket and netinet changes which will likely >> render the network stack broken. > > Good choice of date :-). Maybe you could borrow PHK's axe and have some > fun: Remove the IPv4 stack to encourage the use of IPv6 :-). > > Seriously, thanks for all your efforts in improving FreeBSD. Yeah, it's actually quite funny. I picked the date based on a number of weeks from when things appeared to start stabilizing, and giving a long enough time to appeal for maintainers. Only after I posted did I realize what a good choice it was -- when I mentioned to someone I was breaking TCP on April 1. :-) Robert N M Watson