Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <00fb01c2f6ff$1135b120$646086d9@ellixia> Reply-To: "Elfyn McBratney" From: "Elfyn McBratney" To: "cygwin" , "linda w \(cyg\)" References: <002001c2f6fc$d2021ae0$1403a8c0 AT sc DOT tlinx DOT org> Subject: Re: bash bug report? Minor border case: Date: Sun, 30 Mar 2003 21:57:00 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 > Agreed. Perhaps the naming should be a bit more evident. > I don't reread the list purpose everytime I do a post. Cygwin-packaging or cygwin-app-packag[e/ing] would be a bit more self- > documenting. Nothing more intelligent that a self documenting > name. :-) > -linda Maybe. But that document () is there for a reason, that being list descriptions and perhaps rules. Remebering that setup bugs and package maintainer chit-chat goto cygwin-apps AT cygwin DOT com , bugs in apache, bash or pdksh :-) and the rest of all things Cygwin goto cygwin AT cygwin DOT com , and Cygwin DLL patches goto cygwin-patches AT cygwin DOT com , shouldn't be too hard. I'm not saying this personally just a little post-it for subscribers mailboxes. ;-) Regards, Elfyn McBratney elfyn AT exposure DOT org DOT uk www.exposure.org.uk -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/