public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: siginfo_t missing member si_band
Date: Wed, 16 Oct 2013 16:05:00 -0000	[thread overview]
Message-ID: <20131016160541.GD18358@calimero.vinschen.de> (raw)
In-Reply-To: <394t5950l6akj42eeqfgqb8es4v0c7q0b9@4ax.com>

[-- Attachment #1: Type: text/plain, Size: 915 bytes --]

On Oct 16 15:17, Bengt Larsson wrote:
> Christopher Faylor wrote:
> 
> >I guess so.  In a project that wasn't requestware or wishware it would
> >be a spur for someone to submit code to Cygwin to implement SIGPOLL and
> >it's accompanying siginfo_t handling.  Unfortunately, Cygwin seems to
> >be mainly requestware these days.
> 
> Is a bug report "requestware"? I actually did look at the malloc code
> but I found it very hard to understand.

No, good bugreports with testcases are usually a joy (unless it's in a
part of code the developer hates a lot, but that goes without saying, I
guess).  As for the Doug Lea malloc code, I think there aren't so many
people claiming they fully understand the code.  Except Doug Lea,
probably.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

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

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-15 14:48 Ryan Johnson
2013-10-15 19:42 ` Christopher Faylor
2013-10-15 21:14   ` Ryan Johnson
2013-10-15 22:36     ` Christopher Faylor
2013-10-15 23:15       ` Larry Hall (Cygwin)
2013-10-15 23:16         ` Warren Young
2013-10-16  7:59           ` Corinna Vinschen
2013-10-16 21:27             ` Christopher Faylor
2013-10-17  3:46               ` Ryan Johnson
2013-10-17  8:48                 ` Corinna Vinschen
2013-10-16 13:17       ` Bengt Larsson
2013-10-16 16:05         ` Corinna Vinschen [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=20131016160541.GD18358@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@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).