From owner-freebsd-ports  Sun Sep 21 10:17:53 1997
Return-Path: <owner-freebsd-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id KAA08511
          for ports-outgoing; Sun, 21 Sep 1997 10:17:53 -0700 (PDT)
Received: from istari.home.net (cc158233-a.catv1.md.home.com [24.3.25.17])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA08489
          for <ports@FreeBSD.ORG>; Sun, 21 Sep 1997 10:17:49 -0700 (PDT)
Received: (from sjr@localhost)
	by istari.home.net (8.8.7/8.8.6) id NAA13914;
	Sun, 21 Sep 1997 13:17:44 -0400 (EDT)
Date: Sun, 21 Sep 1997 13:17:44 -0400 (EDT)
From: "Stephen J. Roznowski" <sjr@home.net>
Message-Id: <199709211717.NAA13914@istari.home.net>
To: chuckr@glue.umd.edu, ports@FreeBSD.ORG
Subject: Re: Making ports
In-Reply-To: Mail from 'Chuck Robey <chuckr@glue.umd.edu>'
      dated: Sun, 21 Sep 1997 12:31:06 -0400 (EDT)
Sender: owner-freebsd-ports@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> From: Chuck Robey <chuckr@glue.umd.edu>
> Subject: Making ports
> 
> As a suggestion to porters:
> 
> If you announce a port, or (more likely) post it via GNATS, and don't
> bother to give even the most cursory explanation of what it is or what it
> does, then don't be surprised it everyone decides to ignore it.
> 
> Just giving the filename ISN'T sufficient, not if you want someone to
> volutarily check your port.  It might happen, but it's not terribly
> likely.

Okay, but where is the proper place to remind people to process
ports that have been sent in via send-pr? (and yes, it did have
a multiline description... :-)