sleepy_penguin RubyGem user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: ruby-talk@ruby-lang.org, sleepy-penguin@bogomips.org
Subject: [ANN] sleepy_penguin 3.5.1 - Linux I/O events (and more) for Ruby
Date: Sat, 15 Dec 2018 04:46:51 +0000	[thread overview]
Message-ID: <20181215-sleepy_penguin-3.5.1-rele@sed> (raw)
In-Reply-To: <20170322072733.GA26884@dcvr>

sleepy_penguin provides access to newer, Linux-only system calls to wait
on events from traditionally non-I/O sources.  Bindings to the eventfd,
timerfd, inotify, and epoll interfaces are provided.  Experimental support
for kqueue on FreeBSD (and likely OpenBSD/NetBSD) is also provided.

* homepage: https://bogomips.org/sleepy_penguin/
* git clone https://bogomips.org/sleepy_penguin.git
* Atom feed: https://bogomips.org/sleepy_penguin/NEWS.atom.xml
* mailing list: sleepy-penguin@bogomips.org
* mail archives: https://bogomips.org/sleepy-penguin/
	nntp://news.public-inbox.org/inbox.comp.lang.ruby.sleepy-penguin
	https://bogomips.org/sleepy-penguin/new.atom

Changes:

    sleepy_penguin 3.5.1

    This release fixes some minor things for kqueue and clang
    users.  Not much going on... *yawn*

    6 changes since v3.5.0 (2017-03-22):

          kqueue: ensure close-on-exec flag is set
          kqueue: modernize Struct usage for Ruby 2.5.0dev
          fix 64-to-32-bit truncation warning
          kqueue: get rid of unused variable warnings
          epoll: avoid reduce block capture and ivar requests
          doc: use HTTPS URLS when possible

      reply	other threads:[~2018-12-15  4:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-22  7:27 [ANN] sleepy_penguin 3.5.0 - Linux I/O events (and more) for Ruby Eric Wong
2018-12-15  4:46 ` Eric Wong [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

  List information: https://yhbt.net/sleepy_penguin/

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

  git send-email \
    --in-reply-to=20181215-sleepy_penguin-3.5.1-rele@sed \
    --to=e@80x24.org \
    --cc=ruby-talk@ruby-lang.org \
    --cc=sleepy-penguin@bogomips.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/sleepy_penguin.git/

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