public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: "Ed C. Lueless" <ed.c@lueless.org>
To: The Cygwin-Talk Mailing List <cygwin-talk@cygwin.com>
Subject: Re: once more unto the breech - please try a snapshot so I can  release this thing
Date: Fri, 13 Jan 2006 17:06:00 -0000	[thread overview]
Message-ID: <20060113170622.GA4668@trixie.casa.cgf.cx> (raw)
In-Reply-To: <Pine.GSO.4.63.0601131154590.27020@access1.cims.nyu.edu>

On Fri, Jan 13, 2006 at 11:59:10AM -0500, Igor Peshansky wrote:
>On Fri, 13 Jan 2006, Eric Blake wrote:
>>According to Igor Peshansky on 1/13/2006 9:38 AM:
>>
>>>Besides, this thread has not even mentioned hippos.  How can you have a
>>>cygwin-talk thread with no hippos?  This is outrageous! So, here's the
>>>obligatory mention of hippos: LOOK OUT, THERE'S A HIPPO BEHIND YOU!
>>
>>I beg to differ.  As OP, I most certainly mentioned hippos in
>>http://cygwin.com/ml/cygwin-talk/2006-q1/msg00028.html.
>
>Yes, you did.  Apologies for missing it.  How does one miss a hippo,
>anyway?
>
>>Wait, what's that noise I hear behind me?
>
>Whoosh -- *SPLAT*.  :-)

I don't use Outlook at all.  I use Mutt! It is not that hard
to set up.  It only took a couple of hours and it was
well worth the invstement!

I try to use as little of the Windoze crap as possible!

I tell everyone in my comapny to use CygwIn but I'm hoping
that we're going to switch to linux soon because Cygwin is
*s*l*o*w*.

But, before cfg flames me, I want to point out that he
and Corrina have both done an amazing job getting things
working pn a *sucky* OS!

P.S. "Mailing" was *still* mispelled in the To until I fixed
it.
--
-Ed C. Lueless         Master Programmer
"Love your enemy -- it will drive him nuts." -- Eleanor Doan
"Ed C.  - you are the man!" -- my boss

  reply	other threads:[~2006-01-13 17:06 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-11 14:33 Williams, Gerald S (Jerry)
2006-01-11 16:05 ` Christopher Faylor
2006-01-11 17:33   ` Dave Korn
2006-01-11 22:02     ` One Angry User
2006-01-12  0:08     ` Igor Peshansky
2006-01-12  0:18       ` Igor Peshansky
2006-01-12 10:51         ` Dave Korn
2006-01-12 13:32           ` Igor Peshansky
2006-01-12 21:34             ` Joe Smith
2006-01-12 22:01               ` Ed C. Lueless
2006-01-13  0:07               ` Igor Peshansky
2006-01-13 15:01                 ` Joe Smith
2006-01-13 15:10                   ` Dave Korn
2006-01-13 15:11                   ` Corinna Vinschen
2006-01-13 16:38                   ` Igor Peshansky
2006-01-13 16:49                     ` Eric Blake
2006-01-13 16:59                       ` Igor Peshansky
2006-01-13 17:06                         ` Ed C. Lueless [this message]
2006-01-13 17:15                           ` Dave Korn
2006-01-13 16:54                     ` Dave Korn
2006-01-13 17:00                       ` Igor Peshansky
2006-01-13 17:08                         ` Dave Korn
2006-01-13 17:41                           ` once more unto the breech - please try a snapshot so I canrelease " Igor Peshansky
2006-01-13 17:15                     ` once more unto the breech - please try a snapshot so I can release " Dave Korn
2006-01-13 17:42                       ` Igor Peshansky
2006-01-13 17:59                         ` Dave Korn
2006-01-13 18:48                           ` once more unto the breech - please try a snapshot so I canrelease " Igor Peshansky
2006-01-12  4:30     ` once more unto the breech - please try a snapshot so I can release " Gary R. Van Sickle
2006-01-15  5:20       ` * *
2006-01-15  5:41         ` Gary R. Van Sickle
2006-01-16 10:33         ` Dave Korn
  -- strict thread matches above, loose matches on Subject: below --
2006-01-18 18:13 Williams, Gerald S (Jerry)
2006-01-18 18:27 ` Dave Korn
2006-01-17 15:26 Williams, Gerald S (Jerry)
2006-01-17 15:38 ` Dave Korn
     [not found] <20060111022341.GA31671@trixie.casa.cgf.cx>
2006-01-11 14:13 ` Eric Blake

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=20060113170622.GA4668@trixie.casa.cgf.cx \
    --to=ed.c@lueless.org \
    --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).