public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: "Lee D. Rothstein" <l1ee057@veritech.com>
To: "Cygwin, Talk Amongst Yourselves" <cygwin-talk@cygwin.com>
Subject: Re: Thank you so much..
Date: Tue, 21 Dec 2010 19:37:00 -0000	[thread overview]
Message-ID: <4D1101BC.502@veritech.com> (raw)
In-Reply-To: <7lr1h6hob4pgukdp24e6dm6iesl29h7svm@4ax.com>

On 12/21/2010 1:15 PM, Andrew Schulman wrote:
>> On Tue, Dec 21, 2010 at 07:01:56PM +0100, auto18565658@hushmail.com wrote:
>>> ...setup, for removing the shortcut to mintty in my "Start Menu".
>>>
>>> Retards.
>> My, my, aren't we very brave?
> As Bugs Bunny used to say:  What a maroon.
>

Andrew,

As a member of the elite and precise Cygwin development cadre, you 
should know that
Bugs Bunny still says this; and will say it forever; especially in this 
case. ;-)

Lee

           reply	other threads:[~2010-12-21 19:37 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <7lr1h6hob4pgukdp24e6dm6iesl29h7svm@4ax.com>]

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=4D1101BC.502@veritech.com \
    --to=l1ee057@veritech.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).