README in posix_mq-0.6.0.11.g634a vs README in posix_mq-0.7.0

@@ -30,10 +30,13 @@
 
 * Documented library API
 
 * Includes a generic "posix-mq-rb" command-line tool with manpage.
 
+* {EventMachine}[http://rubyeventmachine.com/] integration via
+  {em-posixmq}[https://github.com/ibc/em-posixmq]
+
 == Install
 
 Operating system support (or library emulation) for POSIX message queues
 is required.  Most modern GNU/Linux distributions support this
 out-of-the-box.
@@ -59,11 +62,11 @@
 {mqueuefs(5)}[http://freebsd.org/cgi/man.cgi?query=mqueuefs]
 kernel module before attempting to use POSIX message queues:
 
     kldload mqueuefs
 
-Our API matches the C api closely, see the RDoc for full API
+Our API matches the POSIX C API closely, see the RDoc for full API
 documentation.  Here is an example of a process communicating
 with itself.  In practice, processes that send will be different
 from processes that receive.
 
     require 'posix_mq'
@@ -103,15 +106,19 @@
 the patch.
 
 We will adhere to mostly the same conventions for patch submissions as
 git itself.  See the Documentation/SubmittingPatches document
 distributed with git on on patch submission guidelines to follow.  Just
-don't email the git mailing list or maintainer with posix_mq patches.
+don't email the git mailing list or maintainer with Ruby posix_mq patches.
 
 == Contact
 
 All feedback (bug reports, user/development discussion, patches, pull
 requests) go to the mailing list: mailto:[e-mail]
+
+Send patches (from "git format-patch") with "git send-email" and do not
+send HTML email or attachments.  We are very responsive to email and you
+will usually get a response within 24-72 hours.
 
 == Mailing List Archives
 
 In addition to the rsync-able archives provided by http://librelist.com/, we
 are also mirrored to