From owner-freebsd-ports  Mon Dec 30 01:22:32 1996
Return-Path: <owner-ports>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id BAA10992
          for ports-outgoing; Mon, 30 Dec 1996 01:22:32 -0800 (PST)
Received: from mail.tky007.tth.expo96.ad.jp (root@tky007.tth.expo96.ad.jp [133.246.32.58])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA10987;
          Mon, 30 Dec 1996 01:22:26 -0800 (PST)
Received: from tky007.tth.expo96.ad.jp (masafumi@localhost [127.0.0.1]) by mail.tky007.tth.expo96.ad.jp (8.8.4/3.4W4-SMTP) with ESMTP id SAA10969; Mon, 30 Dec 1996 18:22:29 +0900 (JST)
Message-Id: <199612300922.SAA10969@mail.tky007.tth.expo96.ad.jp>
To: freebsd-ports@freebsd.org, asami@freebsd.org
Cc: max@wide.ad.jp
Subject: Re: Questions about a ports freeze...
From: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= <max@wide.ad.jp>
X-Mailer: Mew version 1.54 on Emacs 19.28.1, Mule 2.3
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Mon, 30 Dec 1996 18:22:29 +0900
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?

    asami> It is supposed to be cleaned after a port is committed.
    asami> But sometimes the committer never gets around to it.  And
    asami> then once in a while we get a massive warez (or whatever)
    asami> attack and the sysadmin cleans up everything.

    asami> As it is now plainly obvious, this is bad.  Maybe we should
    asami> arrange a different location for ports uploads only.

I think this is because they are in a place where not many committers
have right to remove files from.  So as you suggest, if we can arrange
some other place where committers can touch, the situation would get
much better, I assume.
(Actually, some files I submitted about a year ago still sit there,
but I can't delete it. :)

Max