From owner-freebsd-current  Wed May 15 17:13:23 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id RAA05575
          for current-outgoing; Wed, 15 May 1996 17:13:23 -0700 (PDT)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA05564
          for <current@freebsd.org>; Wed, 15 May 1996 17:13:18 -0700 (PDT)
Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id TAA27225 for current@freebsd.org; Wed, 15 May 1996 19:13:17 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199605160013.TAA27225@dyson.iquest.net>
Subject: Watch out for an upcoming VM commit
To: current@freebsd.org
Date: Wed, 15 May 1996 19:13:17 -0500 (EST)
X-Mailer: ELM [version 2.4 PL24 ME8]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I am preparing a mega-commit for significant VM performance improvments.
I have to do so, because there are requests for implementation of more
new features (mincore, madvise, etc.), and I need to keep the tree in sync.

I don't expect problems, but since the VM mega-commits sometimes cause
*interesting* things to happen, I suggest that you grab a *stable* -current
on Fri or before :-).  If anyone wants or needs a delay, just let me know.

John