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

[Xavier Guimard]

The following commit has been merged in the master branch:
commit 74ca485ce46ec8b09661031b0a8bbd13d0889b4d
Author: Xavier Guimard <x.guimard at free.fr>
Date:   Fri Jan 4 06:19:39 2013 +0100

    Refresh patches (and report some of them)

diff --git a/debian/changelog b/debian/changelog
index d5112fd..4227b55 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,7 +1,7 @@
 libcoro-perl (6.230-1) UNRELEASED; urgency=low
 
   * Imported Upstream version 6.230
-  * Update patches offsets
+  * Update patches
   * Update debian/copyright years
 
  -- Xavier Guimard <x.guimard at free.fr>  Mon, 10 Dec 2012 20:56:22 +0100
diff --git a/debian/patches/spelling.patch b/debian/patches/spelling.patch
index 0873222..24b33ad 100644
--- a/debian/patches/spelling.patch
+++ b/debian/patches/spelling.patch
@@ -1,12 +1,22 @@
 Description: fix a spelling mistake
 Origin: vendor
-Forwarded: no
+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: 2012-12-10
+Last-Update: 2013-01-04
 
 --- a/Coro.pm
 +++ b/Coro.pm
+@@ -731,7 +731,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
+-automatically get assigned a perl interpreter when they are transfered to.
++automatically get assigned a perl interpreter when they are transferred to.
+ 
+ =item $state->is_zombie
+ 
 @@ -1234,7 +1234,7 @@
  by the forks module, which gives you the (i-) threads API, just much
  faster).
@@ -16,6 +26,26 @@ Last-Update: 2012-12-10
  structures between threads using copying semantics, which is very slow -
  shared data simply does not exist. Benchmarks using i-threads which are
  communication-intensive show extremely bad behaviour with i-threads (in
+--- a/Coro/State.pm
++++ b/Coro/State.pm
+@@ -168,7 +168,7 @@
+ everywhere.
+ 
+ If the coderef is omitted this function will create a new "empty"
+-thread, i.e. a thread that cannot be transfered to but can be used
++thread, i.e. a thread that cannot be transferred to but can be used
+ 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 @@
+ 
+ Forcefully destructs the given Coro::State. While you can keep the
+ reference, and some memory is still allocated, the Coro::State object is
+-effectively dead, destructors have been freed, it cannot be transfered to
++effectively dead, destructors have been freed, it cannot be transferred to
+ anymore, it's pushing up the daisies.
+ 
+ =item $state->call ($coderef)
 --- a/README
 +++ b/README
 @@ -1009,7 +1009,7 @@
diff --git a/debian/patches/whatis.patch b/debian/patches/whatis.patch
index 118d428..73cef55 100644
--- a/debian/patches/whatis.patch
+++ b/debian/patches/whatis.patch
@@ -1,7 +1,11 @@
 Description: Add a whatis entry
 Origin: vendor
-Forwarded: no
+Bug: https://rt.cpan.org/Ticket/Display.html?id=82393
+Forwarded: https://rt.cpan.org/Ticket/Display.html?id=82393
 Author: Jonathan Yu <frequency at cpan.org>
+Reviewed-By: Xavier Guimard <x.guimard at free.fr>
+Last-Update: 2013-01-04
+
 --- a/Coro/Intro.pod
 +++ b/Coro/Intro.pod
 @@ -1,3 +1,7 @@

-- 
Debian packaging of libcoro-perl