kgio RubyGem user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <>
Subject: kgio 2.4.0 coming
Date: Thu, 5 May 2011 12:43:05 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Because of Jeremy's important OpenBSD (and possibly other *BSD) fixes,
I'm planning to release 2.4.0 sometime today.

I don't think a 2.3.4 is necessary, since most of the 2.4.0 changes
are backwards-compatible and gem dependencies for Unicorn specifies
"~> 2.3" so folks can just upgrade.

There are also some improvements to dealing with signal interrupts for
1.9.3dev and feature additions which I'll probably use for Rainbows!
down the line (few weeks/months), but none affect currently used
code in Unicorn/Rainbows!

Latest changes pushed to git://
(web browsers:

Eric Wong (15):
      HACKING: updates for wrongdoc vs rdoc
      accept: prepare optional flags argument to accept() wrappers
      *accept methods can take flags argument, like accept4()
      accept: better detect closed files on EINTR/EAGAIN
      read_write: detect closed fd on EINTR
      add test for cross thread close
      gemspec: remove unnecessary require_paths
      gemspec: bump wrongdoc version
      test_autopush: use assert_in_delta for test
      doc: fix trywrite call-seq
      test_autopush: attempting to fix a timing test...
      doc: improve kgio_accept/kgio_tryaccept docs
      extconf: remove unnecessary dir_config statement
      Kgio.poll restarts on interrupt
      test_tcp_connect: disable wait_writable_set test on non-Linux

Jeremy Evans (2):
      connect: zero out hints argument for getaddrinfo
      fix kgio_peek for !KGIO_NOPUSH systems

Eric Wong

           reply	other threads:[~2011-05-05 19:43 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <>]

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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).