ports/150194: Subject: There is no startup script for cassandra

[Mark Linimon]

The following reply was made to PR ports/150194; it has been noted by GNATS.

From: Mark Linimon <linimon at lonesome.com>
To: bug-followup at FreeBSD.org
Cc:  
Subject: Re: ports/150194: Subject: There is no startup script for cassandra
Date: Thu, 24 Mar 2011 02:06:37 -0500

 forwarded from email misfiled in my personal mailbox.
 
 Sorry.
 
 mcl
 
 ----- Forwarded message from Gea-Suan Lin <gslin at gslin.org> -----
 
 Date: Tue, 25 Jan 2011 18:39:26 +0800
 From: Gea-Suan Lin <gslin at gslin.org>
 To: portmgr-feedback at FreeBSD.org
 Cc: gslin at gslin.org
 Subject: Re: FreeBSD ports Problem Reports for ports you maintain
 User-Agent: Mutt/1.5.21 (2010-09-15)
 
 Thanks, please commit this startup script.
 
 On Fri, Jan 21, 2011 at 08:29:50AM +0100, linimon at FreeBSD.org wrote:
 > Dear FreeBSD port maintainer:
 > 
 > As part of an ongoing effort to reduce the number of Problem Reports
 > (PRs) that affect the FreeBSD ports system, we are attempting to
 > identify PRs for ports where the port maintainer may never have been
 > informed about the PRs in the first place, and notify him or her of
 > this fact.
 > 
 > The PRs are listed below.
 > 
 > PR number:          150194
 > PR title:           There is no startup script for databases/cassandra
 > category:           databases
 > portname:           cassandra
 > submitter:          kevin.way at insidesystems.net
 > arrival date:       2010-09-01 18:20:01
 > PR state:           open
 > URL:                http://www.FreeBSD.org/cgi/query-pr.cgi?pr=150194
 > 
 > If these PRs are ones that you are already aware of, please accept
 > our apologies and ignore this message.  (If you wish, we can turn
 > off notifications for individual PRs.)  On the other hand, if you
 > no longer wish to maintain this port (or ports), please reply with
 > a message stating that, and accept our thanks for your efforts in
 > the past.
 > 
 > Every effort has been made to make sure that these PRs really do
 > correspond to a port that you maintain.  However, due to the fact
 > that the PR database does not insist that port PRs be given a
 > category and portname, the best that we can do is to try to guess
 > (algorithmically) and then manually correct the entries that the
 > algorithm gets wrong.  If one of these PRs fits that description,
 > please forward this email to the author of this software, Mark
 > Linimon <linimon at FreeBSD.org>, so that he can attempt to fix the
 > problem in the future.
 > 
 > (Note: more information about each port, including any build errors
 > seen in any of the various build enviornments, can be found at
 > http://portsmon.FreeBSD.org/portoverview.py.)
 > 
 > Thanks for your efforts to help improve FreeBSD.
 
 -- 
 * Gea-Suan Lin  (public key: Using https://keyserver.pgp.com/ to search)
 * If you cannot convince them, confuse them.           -- Harry S Truman
 
 
 ----- End forwarded message -----