[SCM] Debian packaging of libcoro-perl branch, master, updated. debian/6.100-2-22-g20484b7

[Xavier Guimard]

The following commit has been merged in the master branch:
commit 764d8c35858947e18d6ecbc1ae67b35f613599d0
Author: Xavier Guimard <x.guimard at free.fr>
Date:   Sun May 12 08:35:50 2013 +0200

    Update spelling errors patch

diff --git a/debian/patches/spelling.patch b/debian/patches/spelling.patch
index 24b33ad..4f6226f 100644
--- a/debian/patches/spelling.patch
+++ b/debian/patches/spelling.patch
@@ -4,11 +4,11 @@ Bug: https://rt.cpan.org/Ticket/Display.html?id=82392
 Forwarded: https://rt.cpan.org/Ticket/Display.html?id=82392
 Author: gregor herrmann <gregoa at debian.org>
 Reviewed-by: Xavier Guimard <x.guimard at free.fr>
-Last-Update: 2013-01-04
+Last-Update: 2013-05-12
 
 --- a/Coro.pm
 +++ b/Coro.pm
-@@ -731,7 +731,7 @@
+@@ -755,7 +755,7 @@
  Returns true iff this Coro object is "new", i.e. has never been run
  yet. Those states basically consist of only the code reference to call and
  the arguments, but consumes very little other resources. New states will
@@ -17,7 +17,7 @@ Last-Update: 2013-01-04
  
  =item $state->is_zombie
  
-@@ -1234,7 +1234,7 @@
+@@ -1258,7 +1258,7 @@
  by the forks module, which gives you the (i-) threads API, just much
  faster).
  
@@ -28,7 +28,7 @@ Last-Update: 2013-01-04
  communication-intensive show extremely bad behaviour with i-threads (in
 --- a/Coro/State.pm
 +++ b/Coro/State.pm
-@@ -168,7 +168,7 @@
+@@ -178,7 +178,7 @@
  everywhere.
  
  If the coderef is omitted this function will create a new "empty"
@@ -37,7 +37,7 @@ Last-Update: 2013-01-04
  to save the current thread state in (note that this is dangerous, as no
  reference is taken to ensure that the "current thread state" survives,
  the caller is responsible to ensure that the cloned state does not go
-@@ -237,7 +237,7 @@
+@@ -247,7 +247,7 @@
  
  Forcefully destructs the given Coro::State. While you can keep the
  reference, and some memory is still allocated, the Coro::State object is
@@ -46,9 +46,18 @@ Last-Update: 2013-01-04
  anymore, it's pushing up the daisies.
  
  =item $state->call ($coderef)
+@@ -336,7 +336,7 @@
+ 
+ =head3 METHODS FOR C CONTEXTS
+ 
+-Most coros only consist of some Perl data structures - transfering to a
++Most coros only consist of some Perl data structures - transferring to a
+ coro just reconfigures the interpreter to continue somewhere else.
+ 
+ However. this is not always possible: For example, when Perl calls a C/XS function
 --- a/README
 +++ b/README
-@@ -1009,7 +1009,7 @@
+@@ -1033,7 +1033,7 @@
      evidenced by the forks module, which gives you the (i-) threads API,
      just much faster).
  

-- 
Debian packaging of libcoro-perl