From owner-freebsd-stable Wed May 31 18:20: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id EC97E37BF63; Wed, 31 May 2000 18:19:54 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id TAA48128; Wed, 31 May 2000 19:19:52 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id TAA26057; Wed, 31 May 2000 19:19:29 -0600 (MDT) Message-Id: <200006010119.TAA26057@harmony.village.org> To: Kris Kennaway Subject: Re: GENERIC 4.0 kernel compile fails on in_cksum.c Cc: Andy Farkas , freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Wed, 31 May 2000 01:45:33 PDT." References: Date: Wed, 31 May 2000 19:19:29 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Kris Kennaway writes: : AFAIK, we've never claimed to support upgrades to major (.0) releases from : anything other than the most recent previous release, and with good : reason. We have an upgrade path which is well tested and works, so let's : just leave it at that. That's not true. We did claim to support source upgrades from 2.2.5 or later to 3.x for x <= 2. And it worked as well. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message