Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com From: Chris Faylor Date: Tue, 22 Aug 2000 20:42:28 -0400 To: cygwin-apps AT sources DOT redhat DOT com Subject: Re: perl-5.6.0 ready for test! (IMPORTANT READ THIS MESSAGE ON MAINTAINER STATUS!) Message-ID: <20000822204228.B770@cygnus.com> Reply-To: cygwin-apps AT sources DOT redhat DOT com Mail-Followup-To: cygwin-apps AT sources DOT redhat DOT com References: <8600BF007197944F8DD3906E40CB428005D83C AT itdomain001 DOT itdomain DOT net DOT au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <8600BF007197944F8DD3906E40CB428005D83C@itdomain001.itdomain.net.au>; from robert.collins@itdomain.com.au on Wed, Aug 23, 2000 at 10:39:46AM +1000 On Wed, Aug 23, 2000 at 10:39:46AM +1000, Robert Collins wrote: >The set of mailing lists sounds almost like a set of FAQ's - maintained >by one person per FAQ... > >Perhaps a set of FAQ's and a matching set of mail alias's >ie PERL-CYGWIN FAQ hanging off the existing FAQ at the index, and >perl-cygwin AT sources DOT redhat DOT com - goes to the perl maintainer, and they >/dev/null or update the FAQ as appropriate. > >I think separating support for the application issues from the "kernel" >or portability layer is a very good idea. Hmm. I like this! We could even set up FAQ-O-MATIC on the cygwin web pages. cgf