From: "Gary R. Van Sickle" <g.r.vansickle@worldnet.att.net>
To: "'The Cygwin-Talk Maiming List'" <cygwin-talk@cygwin.com>
Subject: RE: random "fork: Resource temporarily unavailable" etc.
Date: Fri, 23 Jun 2006 00:35:00 -0000 [thread overview]
Message-ID: <005801c6965c$ed9720e0$020aa8c0@DFW5RB41> (raw)
In-Reply-To: <20060622160012.GC19879@trixie.casa.cgf.cx>
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?:
> From: Christopher Faylor
> Sent: Thursday, June 22, 2006 11:00 AM
> To: cygwin [not cygwin-talk] at cygwin dot com
> Subject: Re: random "fork: Resource temporarily unavailable"
>
> [snip cygwin-related discussion]
>
> So, when will sshd be fixed? It seems to me that if cygwin
> wants to be taken seriously it should try to work nicely with
> other software!!!
>
> cgf
Larry Hall wrote:
http://cygwin.com/ml/cygwin/2006-06/msg00653.html
http://cygwin.com/ml/cygwin/2006-06/msg00641.html
--
Gary R. Van Sickle
next parent reply other threads:[~2006-06-23 0:35 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 [this message]
2006-06-23 6:43 ` Christopher Faylor
2006-06-23 9:17 ` 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='005801c6965c$ed9720e0$020aa8c0@DFW5RB41' \
--to=g.r.vansickle@worldnet.att.net \
--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).