From owner-freebsd-current  Tue Mar  5 18:18:39 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id SAA18138
          for current-outgoing; Tue, 5 Mar 1996 18:18:39 -0800 (PST)
Received: from sunrise.cs.berkeley.edu (sunrise.CS.Berkeley.EDU [128.32.38.121])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA18133
          for <freebsd-current@freebsd.org>; Tue, 5 Mar 1996 18:18:36 -0800 (PST)
Received: (from asami@localhost) by sunrise.cs.berkeley.edu (8.6.12/8.6.12) id SAA08786; Tue, 5 Mar 1996 18:20:42 -0800
Date: Tue, 5 Mar 1996 18:20:42 -0800
Message-Id: <199603060220.SAA08786@sunrise.cs.berkeley.edu>
To: jkh@time.cdrom.com
CC: freebsd-current@freebsd.org
In-reply-to: <694.826078249@time.cdrom.com> (jkh@time.cdrom.com)
Subject: Re: 2.2-960226-SNAP now on ftp.freebsd.org
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-current@freebsd.org
Precedence: bulk

 * 				    or we need to put ports and packages
 * *under* the release directories and stop offering them at the top in
 * their own hierarchy.  The current situation is simply gross.

Actually, I think this is what we did last time, and I thought you
were pulling in the ports/packages from there until you send me a mail 
saying "Argh!  The 2.1R sysinstall is pulling in the packages from the 
top level, and is getting the -current version!". :)

Why don't we just move everything down one level?  Wherever the
top level directory is going to be (whether it's a snap or a release), 
we can just populate it with appropriate symlinks and everything's
going to work like a snap (no pun intended).

Satoshi