From: One Angry User <angry@lusers.org>
To: The Cygwin-Talk Maiming List <cygwin-talk@cygwin.com>
Subject: Re: cygwin and multi-gnome-terminal-1.6.
Date: Fri, 21 Apr 2006 17:34:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.63.0604211333360.8777@access1.cims.nyu.edu> (raw)
In-Reply-To: <44490A4D.3070603@tibco.com>
On a sunny Friday, the 21st day of April, 2006, mwoehlke's computer deigned to emit the following stream of bytes:
> Eric Blake wrote:
> > Hint - reread http://cygwin.com/lists.html about the various
> > list descriptions. This is the mindless chatter list, not the
> > technical answers list (try cygwin instead of cygwin-talk if
> > you don't want random answers involving hippos and other
> > oddities).
>
> Shh! Be vewwy, vewwy quiet... I'm hunting...
>
> ...porcupine!
> (Bet you thought I'd say "Hippo" :-))
"Wabbit", actuawwy...
OAU
next prev parent reply other threads:[~2006-04-21 17:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 1:44 Eric Blake
2006-04-21 15:25 ` Christopher Faylor
2006-04-21 16:37 ` mwoehlke
2006-04-21 17:34 ` One Angry User [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-20 20:21 Mariusz
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=Pine.GSO.4.63.0604211333360.8777@access1.cims.nyu.edu \
--to=angry@lusers.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).