public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: "I can't even say the word 'Lake Titicaca' without giggling like
	a schoolgirl" <cygwin-talk@cygwin.com>
Subject: Re: WTF proposed acronym
Date: Sat, 21 Nov 2009 22:15:00 -0000	[thread overview]
Message-ID: <4B086A15.9020506@gmail.com> (raw)
In-Reply-To: <BLU113-W39CED3A879F84820CD753BEA00@phx.gbl>

Mike Marchywka wrote:

> ----------------------------------------
>> Date: Sat, 21 Nov 2009 21:00:51 +0000
>> From: dave.korn.cygwin@

  Kindly lose that shit, I get enough spam as it is!

>> Lee D. Rothstein wrote:
>>
>>> And, you gotta love any acronym of this sort that begins
>>> with MIT, ends with two TPs, has an MD in the middle,
>>> contains no obscentities and refers to man's best friend.
>> I am the great Cornholio! I need TP for my bunghole! I come from Lake
>> Obscentiticaca in Nicaragua!
> 
> wtf is lake Obscentiticaca, I've seen beavis and butthead,

  Cornholio often claims to come from Lake Titicaca.
  Lee typo'd obscenities in a way that made it sound like "obscene titties".
  I put the two together.

> I've also seem dumber confusion than with windoze variabbles.
> 
> Without knowing wtf the original poster could have been doing, using
> windoze variable at some point could have been important and maybe
> there is some obscure problem with unknown bloda. 

  So your current explanation is that you don't know what the OP was doing, or
what might have happened, or what caused whatever it was that happened to
happen, but you wanted to point out that it might have had something to do
with environment variables, and that some other unknown thing might have had
an unknown effect on them in some unknown way?  Uh, OK.

    cheers,
      DaveK

  reply	other threads:[~2009-11-21 22:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b0ddfae80911201019m4832a7f9k684b502b52a05ce3@mail.gmail.com>
     [not found] ` <b0ddfae80911201104g705e4a1bkb2bd526a50eb8ea2@mail.gmail.com>
     [not found]   ` <20091121121218.GZ29173@calimero.vinschen.de>
     [not found]     ` <b0ddfae80911210516t36d42aadj6496b054a9f694c8@mail.gmail.com>
     [not found]       ` <20091121173625.GB9003@ednor.casa.cgf.cx>
     [not found]         ` <b0ddfae80911211004j3046a795y9ab3a3ba7374a859@mail.gmail.com>
     [not found]           ` <4B083047.8050101@gmail.com>
     [not found]             ` <b0ddfae80911211027t6f912979ic1fbf2d31aa4441@mail.gmail.com>
     [not found]               ` <4B08376D.9060408@gmail.com>
     [not found]                 ` <20091121185049.GA13903@ednor.casa.cgf.cx>
     [not found]                   ` <b0ddfae80911211125j57f6a073haed14a7cff591d6@mail.gmail.com>
2009-11-21 19:48                     ` [OT] Re: Use of Dual Core causes random failures building OpenJDK Dave Korn
2009-11-21 19:48                   ` WTF proposed acronym Lee D. Rothstein
2009-11-21 20:46                     ` Dave Korn
2009-11-21 21:37                       ` Mike Marchywka
2009-11-21 22:15                         ` Dave Korn [this message]
2009-11-21 22:35                           ` Mike Marchywka
2009-11-21 22:49                             ` Dave Korn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B086A15.9020506@gmail.com \
    --to=dave.korn.cygwin@googlemail.com \
    --cc=cygwin-talk@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).