--- Coro/Changes	2007/11/01 08:41:14	1.288
+++ Coro/Changes	2007/12/27 21:52:21	1.310
@@ -5,16 +5,58 @@
       (which is cool in a lot of important aspects (failures!),
       but very lacking in others (higher level ipc)).
 
+4.35
+	- "bt" debug command now displays any exceptions
+          from longmess.
+	- allow backtraces in coroutines blocked in Coro::EV,
+          at a <1% speed hit.
+
+4.34 Sat Dec 22 17:49:53 CET 2007
+	- upgrade to EV version 2.0 API.
+
+4.33 Mon Dec 17 08:36:12 CET 2007
+	- make Coro::AIO etc. loadable in the absence of EV.
+
+4.32 Mon Dec 17 07:46:02 CET 2007
+	- majorly improved Coro::Handle's performance with Coro::EV.
+        - implemented the until now mythical Coro::BDB module.
+        - specialcase EV in Coro::AIO and Coro::BDB for extra speed.
+
+4.31 Wed Dec  5 12:32:39 CET 2007
+	- remove warn statement form Coro::Util.
+
+4.3  Tue Dec  4 20:33:14 CET 2007
+	- calls to the idle function could cause stack corruption
+          when the stack changed.
+	- do no longer rely on the presence of EV::DNS if EV is used
+          (because it is gone), but instead take avdantage of EV::ADNS
+          if available.
+        - add ($) prototypes to all functions in Coro::Storable.
+        - use a conventional (safer) idle callback in Coro::EV.
+        - do accept quickly in Coro::Debug to avoid endless loops.
+
+4.22 Fri Nov 30 16:04:04 CET 2007
+	- really use optimised versions for Event and EV in Coro::Util
+          and Coro::Handle.
+
+4.21 Sun Nov 25 10:48:59 CET 2007
+	- fix a spurious memory read.
+        - Coro::EV no longer keeps the eventloop "alive".
+
+4.2  Fri Nov  9 20:47:05 CET 2007
 	- enable/disable tracing from a new coroutine, not a pooled one.
         - fix a memleak in Coro::Event.
         - removed killall call from fork_eval.
         - made sure store_fd is already loaded so that fork_eval
           does not have to parse autoload in each subprocess.
         - only use assembly method if -O switch is in $Config{optimize}.
-#        - if the event model is EV, use EV::DNS to resolve
-#          stuff in Coro::Util.
+        - add (optional) Coro::EV module, so far the best event loop module
+          directly supported by Coro.
+        - if the event model is EV, use EV::DNS to resolve
+          stuff in Coro::Util.
         - don't get confused by multiple event notifications in Coro::Handle.
         - initial support for EV (libevent interface).
+        - require Event and EV using configure_requires, to force their existance.
 
 4.13 Wed Oct 24 07:26:45 CEST 2007
 	- add Coro::Storable::blocking_thaw.