From owner-freebsd-current Tue Apr 2 18:55:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA29085 for current-outgoing; Tue, 2 Apr 1996 18:55:51 -0800 (PST) Received: from haywire.DIALix.COM (root@haywire.DIALix.COM [192.203.228.65]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA28494 for ; Tue, 2 Apr 1996 18:49:23 -0800 (PST) Received: (from news@localhost) by haywire.DIALix.COM (8.7.5/8.7.3) id KAA17481 for freebsd-current@freebsd.org; Wed, 3 Apr 1996 10:48:22 +0800 (WST) X-Authentication-Warning: haywire.DIALix.COM: news set sender to usenet-request@haywire.dialix.com using -f Received: from GATEWAY by haywire.DIALix.COM with netnews for freebsd-current@freebsd.org (problems to: usenet@haywire.dialix.com) To: freebsd-current@freebsd.org Date: 2 Apr 96 15:35:41 GMT From: peter@jhome.DIALix.COM (Peter Wemm) Message-ID: Organization: DIALix Services, Perth, Australia. References: (Warner, Losh), <199604010342.UAA11579@rover.village.org> Subject: Re: We need to do another XFree86 release for -current someday soon.. Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk imp@village.org (Warner Losh) writes: [...] >If there are *OTHER* reasons or plans that will require a major rev >bump, please let communicate that fact. If that is indeed the plans, >then there is no reason to continue this debate, since we gotta do it. [...] Another likely candidate for needing the 2.2->3.0 revision bump is that we may use the 4.4Lite-2 calling sequence for getvfsbyname(). Also, the mmap() etc syscalls have changed types, but I dont think there's a real incompatability there.. >Warner -Peter