public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin-talk@cygwin.com
Subject: Re: siginfo_t missing member si_band
Date: Wed, 16 Oct 2013 23:28:00 -0000	[thread overview]
Message-ID: <525F2100.7060506@gmail.com> (raw)
In-Reply-To: <20131016212702.GB4370@ednor.casa.cgf.cx>

Il 10/16/2013 11:27 PM, Christopher Faylor ha scritto:
> On Wed, Oct 16, 2013 at 09:59:25AM +0200, Corinna Vinschen wrote:
>> On Oct 15 17:16, Warren Young wrote:
>>> On 10/15/2013 17:14, Larry Hall (Cygwin) wrote:
>>>> Any chance of getting a Cygwin implementation of a coffee-maker then? ;-)
>>>
>>> Well, it *is* a standard.  RFC 2324: http://tools.ietf.org/html/rfc2324
>>
>> I'd expect there's an OSS library somewhere around which implements it.
>> Or maybe we could just grab the BSD code...
>
> I don't see how SIGPOLL could be implemented by copying BSD code.  It
> would have to rely on modifying the fhandler code.
>

Hi CGF,
I had the impression Corinna was referring to rfc2324
(Hyper Text Coffee Pot Control Protocol)
not to the original SIGPOLL...

Marco




       reply	other threads:[~2013-10-16 23:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <525D55B3.3050002@cs.utoronto.ca>
     [not found] ` <20131015194242.GA2368@ednor.casa.cgf.cx>
     [not found]   ` <525DB015.1010707@cs.utoronto.ca>
     [not found]     ` <20131015223645.GB7490@ednor.casa.cgf.cx>
     [not found]       ` <525DCC6F.7000104@cygwin.com>
     [not found]         ` <525DCCDC.9010302@etr-usa.com>
     [not found]           ` <20131016075925.GW18358@calimero.vinschen.de>
     [not found]             ` <20131016212702.GB4370@ednor.casa.cgf.cx>
2013-10-16 23:28               ` marco atzeri [this message]
2013-10-17  8:43                 ` Corinna Vinschen

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=525F2100.7060506@gmail.com \
    --to=marco.atzeri@gmail.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).