On Tue, Oct 26, 2004 at 01:51:43PM -0400, Igor Pechtchanski wrote: >On Tue, 26 Oct 2004, Christopher Faylor wrote: > >> On Tue, Oct 26, 2004 at 01:22:53PM +0100, Dave Korn wrote: >> >> -----Original Message----- >> >> From: cygwin-owner On Behalf Of asmith >> >> Sent: 26 October 2004 13:18 >> > >> >> 0a.important.mail >> > >> > Not so important you have to send it every ten minutes! >> > >> >> RFC not in list >> >> >> >> Request for Comment >> > >> > My comment is that it's not cygwin-specific. >> >> And, hasn't been used very much, if at all for cygwin. >> >> Maybe we need a disclaimer at the top of the acronym page which asks >> people not to send in their favorite acronyms unless they pertain to >> something which has pertinence to the cygwin mailing lists. > >Heh... > >Isn't what there is now: > > This document should present most acronyms you're likely to find > on the Cygwin mailing list, with an explanation and a brief > history for some. If you can't find an acronym you're looking for > here, try another acronym resource, like The Canonical Acronym > List or AcronymFinder.com. > >and > > I will add more acronyms as I encounter them on the list. > >clear enough? Guess not... I'll think of some better ways of saying >this.
I was thinking of a specific enjoinder *not* to send "out of the blue" suggestions unless you've been reading the list for a while and are familiar with the "cygwin mailing list culture". Yeah. That'll work. Or, as a guy I used to work with was fond of saying "Just use common sense!" cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
