--- Coro/Changes	2007/10/08 00:47:19	1.267
+++ Coro/Changes	2007/10/25 08:13:59	1.283
@@ -5,9 +5,26 @@
       (which is cool in a lot of important aspects (failures!),
       but very lacking in others (higher level ipc)).
 
-4.1
+	- enable/disable tracing from a new coroutine, not a pooled one.
+        - fix a memleak in Coro::Event.
+
+4.13 Wed Oct 24 07:26:45 CEST 2007
+	- add Coro::Storable::blocking_thaw.
+        - use a vastly more complicated technique to localise
+          $SIG{__WARN/DIE__} that also works on perls <= 5.8.8.
+        - use a coroutine for the idle callback Coro::Event,
+          instead of running Event in the current coroutine context.
+          This also catches recursive invocations.
+        - actually report fork errors in gethostbyname and inet_aton.
+
+4.11 Thu Oct 11 02:40:24 CEST 2007
+	- port to threaded perls.
+
+4.1  Thu Oct 11 02:38:16 CEST 2007
       	- incompatible change: $SIG{__DIE__} and $SIG{__WARN__} will now
           be local to each coro (see Coro::State).
+        - incompatible change: for very deep reasons, cede and cede_notself
+          cannot return anything, so nothing will be returned.
 	- possibly bring back 5.10 compatibility (untested).
         - work around stupid (and wrong) warning on 5.10 :(.
 	- overlay the saved state over the context stack. This saves
@@ -18,6 +35,14 @@
         - Coro::Storable::blocking_* did not properly lock
           resulting in races between coroutines.
         - added Coro::Storable::guard.
+        - stopping to trace a coroutine could destroy the cctx of
+          an unrelated coroutine.
+        - explain the relationship between Perl and C coroutines in
+          more detail in Coro::State.
+        - Coro::Util::inet_aton did not short-circuit dotted quad forms,
+          causing a fork per resolve. This also affected Coro::Socket.
+        - switch to a separate stack in $coro->call/eval to avoid
+          invalidating pointers.
 
 4.03 Sat Oct  6 21:24:00 CEST 2007
 	- added Coro::throw method.