From owner-freebsd-ports  Fri Jul  5 10:49:21 1996
Return-Path: owner-ports
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id KAA14948
          for ports-outgoing; Fri, 5 Jul 1996 10:49:21 -0700 (PDT)
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA14932
          for <ports@freebsd.org>; Fri, 5 Jul 1996 10:49:18 -0700 (PDT)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id KAA01776; Fri, 5 Jul 1996 10:48:27 -0700 (PDT)
Date: Fri, 5 Jul 1996 10:48:27 -0700 (PDT)
Message-Id: <199607051748.KAA01776@silvia.HIP.Berkeley.EDU>
To: ache@nagual.ru
CC: ports@freebsd.org
In-reply-to: <199607051658.UAA00389@nagual.ru> (ache@nagual.ru)
Subject: Re: When ports code freeze will be lifted?
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

When the release goes out.

 * I have lots of updates hangs waiting...

That doesn't mean no updates can go in, send me a mail and I'll
approve them on per-item basis.  In general, ports that are required
by a lot of others (e.g., jpeg) and large ports have less chance to go 
in.

Satoshi