fix compilation on solaris with new sunww compilers (closes #416)
add licenses to gemspec

so rubygems.org can display them. 
Merge pull request #421 from pivotal-cloudplanner/patch-1

add licenses to gemspec
Fix crash on attach/detach in the same tick
Merge pull request #427 from pietern/attach-detach

Fix crash on attach/detach in the same tick
fix idle test with epoll (cc #427)
fix infinite loop in heartbeat dispatch when system time is changed (closes #428)
fix EM.stop latency when timers exist (closes #426)
fix rake-compiler hacks when cross-compile env is missing
Fix for ../../../../ext/ed.cpp:987: error: ISO C++ forbids variable-size array ‘iov’

No standards-compliant compiler should have allowed this through.
Fix compiler warnings

Just to trigger a build, really
Fix indentation in README
Merge pull request #434 from chocoby/fix_indentation

Fix indentation in README
Bug fix for OS_WIN32: Replaced errno with WSAGetLastError() where result is compared with WSAE... codes.

Per http://msdn.microsoft.com/en-us/library/windows/desktop/ms737828%28v=vs.85%29.aspx
Error codes set by Windows Sockets are not made available through the
errno variable.

Comparison of errno values with WSAE codes was causing EventMachine
to spontaneously close socket connections when the errno value didn't
match the expected WSAE codes.
Merge pull request #433 from johnsyweb/i686-apple-darwin11-llvm-gcc-4.2-fix

ISO C++ forbids variable-size array ‘iov’
Make ScheduleClose() idempotent

I think this fixes issue #441.

8b613d0 changed the `select` timeout to zero in the case where
NumCloseScheduled > 0. It seems that in certain circumstances (for
example, if `close_connection` is called in a connection's `unbind`)
NumCloseScheduled would get incremented twice, but only decremented
once, thus never again reaching zero for the lifetime of the reactor.

The user-observed effect was that one CPU core would be pegged at 100%,
because the zero `select` timeout caused us to go around the select loop
without any pause.

Changing it so that it is safe to ScheduleClose() multiple times seems
like the cleanest solution to the problem.
Merge pull request #445 from ept/double-close

Make ScheduleClose() idempotent
correct reactor_running? to return false after a process running a reactor forked
Merge pull request #455 from SamSaffron/master

Correct reactor_running? to return false after a process forks
add get_file_descriptor