From owner-freebsd-ports  Mon Jul 29 16:27:56 1996
Return-Path: owner-ports
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id QAA29731
          for ports-outgoing; Mon, 29 Jul 1996 16:27:56 -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 QAA29724
          for <FreeBSD-Ports@FreeBSD.org>; Mon, 29 Jul 1996 16:27:54 -0700 (PDT)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id QAA01198; Mon, 29 Jul 1996 16:27:47 -0700 (PDT)
Date: Mon, 29 Jul 1996 16:27:47 -0700 (PDT)
Message-Id: <199607292327.QAA01198@silvia.HIP.Berkeley.EDU>
To: chuckr@Glue.umd.edu
CC: roberto@keltia.freenix.fr, FreeBSD-Ports@FreeBSD.org
In-reply-to: <Pine.OSF.3.91.960729183625.869C@carrier.eng.umd.edu> (message from Chuck Robey on Mon, 29 Jul 1996 18:38:59 -0400 (EDT))
Subject: Re: place for new ports
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-ports@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

 * OK.  I've never used gnats myself, probably should.  We need to have 
 * something in the FreeBSD www site, that explicitly gives those 
 * instructions, for when you introduce a new port.  I think it's a great 
 * idea to do this, so I can just take a look at the gnats list for ports 
 * that need to be done.  I've tried just saving the mails of new ports, and 
 * it's so busy, it's crazy.  I'd never keep it straight.

Ok, I'll add it to the "porting applications" section of the handbook.

Satoshi