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: <40073C5E.8060303@engr.uconn.edu> Date: Thu, 15 Jan 2004 20:20:30 -0500 From: Orlando Echevarria Reply-To: orlando AT engr DOT uconn DOT edu Organization: School of Engineering - University of Connecticut User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: OLOCA References: <400702D3 DOT 7030802 AT engr DOT uconn DOT edu> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 16 Jan 2004 01:23:18.0915 (UTC) FILETIME=[52BA2530:01C3DBCF] no problem! O -- Orlando Echevarria Webmaster and Developer University of Connecticut - School of Engineering 261 Glenbrook Road, Unit 2237 Storrs, CT Phone: 1(860)486-5394 EMail: orlando AT engr DOT uconn DOT edu Igor Pechtchanski wrote: > On Thu, 15 Jan 2004, Orlando Echevarria wrote: > > >>Rollin' on the floor laughing my ass [off | out] = ROFLMAO >>Rollin' on the floor Lauhging = ROFL >> >>Ta Ta for now = TTFN >>Talk to you later = TTYL >> >>Orlando > > > Orlando, > > I appreciate the input. However, I don't intend the OLOCA to be the > all-inclusive list of all possible acronyms -- there are much better lists > that accomplish this job, two of which are even linked to from the OLOCA > intro. The approach I've taken so far is: if I see an acronym appear more > than once on the Cygwin lists, or if it's Cygwin-specific, or if I > particularly like it (hey, being the maintainer has to have its quirks!), > I include it in the OLOCA. So, in summary, if you have an acronym that > you like and frequently use, and if you use it on any Cygwin list, I'm > likely to include it in the OLOCA. > Igor -- 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/