From owner-freebsd-ports Sat Dec 28 16:58:56 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA06441 for ports-outgoing; Sat, 28 Dec 1996 16:58:56 -0800 (PST) Received: from dfw-ix3.ix.netcom.com (dfw-ix3.ix.netcom.com [206.214.98.3]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA06436 for ; Sat, 28 Dec 1996 16:58:54 -0800 (PST) Received: from baloon.mimi.com (sjx-ca56-03.ix.netcom.com [205.186.122.67]) by dfw-ix3.ix.netcom.com (8.6.13/8.6.12) with ESMTP id QAA19687; Sat, 28 Dec 1996 16:58:20 -0800 Received: (from asami@localhost) by baloon.mimi.com (8.8.4/8.6.12) id QAA16337; Sat, 28 Dec 1996 16:58:16 -0800 (PST) Date: Sat, 28 Dec 1996 16:58:16 -0800 (PST) Message-Id: <199612290058.QAA16337@baloon.mimi.com> To: m230761@ingenieria.ingsala.unal.edu.co CC: ports@freebsd.org In-reply-to: (message from Pedro Giffuni on Fri, 20 Dec 1996 20:32:22 -0500 (EST)) Subject: Re: Questions about a ports freeze... From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * 1) Is /pub/FreeBSD/incoming/ cleaned towards the end of freezes, after a * port is comitted, or is it never cleaned? It is supposed to be cleaned after a port is committed. But sometimes the committer never gets around to it. And then once in a while we get a massive warez (or whatever) attack and the sysadmin cleans up everything. As it is now plainly obvious, this is bad. Maybe we should arrange a different location for ports uploads only. * 2) Can I still submit ports for a future release during the freeze? Sure. But if it is for "future release"s only, then it won't be committed during the freeze, as there are no branches in the ports tree. Actually, if it works fine for the current release, it may even be committed during the freeze (nothing's different from normal times, except it needs my permission). Satoshi