From: "Dave Korn" <dave.korn@artimi.com>
To: "'not that old one again!'" <cygwin-talk@cygwin.com>
Subject: RE: random "fork: Resource temporarily unavailable" etc.
Date: Fri, 23 Jun 2006 09:17:00 -0000 [thread overview]
Message-ID: <00d601c696a5$d33405d0$a501a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <005801c6965c$ed9720e0$020aa8c0@DFW5RB41>
On 23 June 2006 01:35, Gary R. Van Sickle wrote:
> Why do off-topic and Cygwin-content-free posts such as the following
> continue to appear on the cygwin-at list, instead of the more appropriate
> cygwin-talk-at list?:
>
<knocks on door> Delivery man! Delivery man!
<walks in, wearing dodgy second-hand UPS delivery man's uniform, about four
sizes too large, purchased from burglary aids^W^Wfancy dress section of eBay,
looks around>
Who ordered the cheese? Ah, it must be you.
<hands Gary small round slightly smelly parcel, walks out>
cheers,
DaveK
--
Can't think of a witty .sigline today....
prev parent reply other threads:[~2006-06-23 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060622160012.GC19879@trixie.casa.cgf.cx>
2006-06-23 0:35 ` Gary R. Van Sickle
2006-06-23 6:43 ` Christopher Faylor
2006-06-23 9:17 ` Dave Korn [this message]
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='00d601c696a5$d33405d0$a501a8c0@CAM.ARTIMI.COM' \
--to=dave.korn@artimi.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).