raindrops RubyGem user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: raindrops@librelist.com
Subject: Re: latest Raindrops::Watcher changes in raindrops.git
Date: Mon, 21 Mar 2011 11:19:52 -0700	[thread overview]
Message-ID: <20110321181952.GA6277@dcvr.yhbt.net> (raw)
In-Reply-To: 20110318094637.GA3526@dcvr.yhbt.net

Eric Wong <normalperson@yhbt.net> wrote:
> I've made some attempts at UI/UX[1] improvements in raindrops.git:
> 
> * added title attributes to elements on index page to help navigation
> * RDoc examples point to the demo site instead of example.com
> * set Expires headers for cache invalidation
> * prevent Rack::Deflater from buffering with "Cache-Control: no-transform"
> * add link to the Watcher documentation
> 
> It's all running at http://raindrops-demo.bogomips.org/
> 
> Any other recommendations to make it easier to navigate for users?

I haven't thought of any other user-visible changes, a few more internal
cleanups I just pushed out to "master" on git://bogomips.org/raindrops.git
below.  I think I'll release 0.6.0 today...

  commit 14423a47266bbb37fe0b2fe5f24cef9e26037e38
  Author: Eric Wong <normalperson@yhbt.net>
  Date:   Mon Mar 21 11:12:59 2011 -0700

      inet_diag: no need to rely on sin6_addr internals
      
      Seems to breaks under newer libc headers (on Debian sid).

  commit 4331e3f461af6d66bc8de48c336ece0938e3b59e
  Author: Eric Wong <normalperson@yhbt.net>
  Date:   Mon Mar 21 11:10:10 2011 -0700

      extconf: remove check for rb_struct_alloc_noinit()
      
      We no longer use it.

  commit f6af45add8c900b02f2b88617a765fa610fbe9aa
  Author: Eric Wong <normalperson@yhbt.net>
  Date:   Mon Mar 21 11:01:57 2011 -0700

      inet_diag: fix build under MRI 1.8.7

  commit 877433494e4a848d6c6a10d0e6521061e6a10118
  Author: Eric Wong <normalperson@yhbt.net>
  Date:   Mon Mar 21 10:57:30 2011 -0700

      inet_diag: FD_CLOEXEC for inet_diag sockets by default
      
      Very few programs can take advantage of inheriting FDs
      across exec() boundaries, and inet_diag sockets have no
      reason to be used in this way.

  commit a5d552d90942fe3c3d1adfc809638fd78992da6e
  Author: Eric Wong <normalperson@yhbt.net>
  Date:   Mon Mar 21 10:46:58 2011 -0700

      inet_diag: use rb_thread_io_blocking_region under 1.9.3dev
      
      It can detect cross-thread close() calls

  commit f86b02018a4195e199136eb0bd8d127d01cae154
  Author: Eric Wong <normalperson@yhbt.net>
  Date:   Mon Mar 21 10:27:59 2011 -0700

      watcher: remove redundant Rack::Response
      
      No need to duplicate code

-- 
Eric Wong


      reply	other threads:[~2011-03-21 18:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-18  9:46 latest Raindrops::Watcher changes in raindrops.git Eric Wong
2011-03-21 18:19 ` 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/raindrops/

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

  git send-email \
    --in-reply-to=20110321181952.GA6277@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=raindrops@librelist.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.
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/raindrops.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).