[SCM] Debian packaging of libclass-c3-perl branch, master, updated. debian/0.24-1-11-g30a668c

[gregor herrmann]

The following commit has been merged in the master branch:
commit db73314588183f9fb38495221d3f07dc743a8b34
Author: gregor herrmann <gregoa at debian.org>
Date:   Thu Jul 4 19:24:12 2013 +0200

    Drop spelling patch, fixed upstream.

diff --git a/debian/patches/fix-pod-spelling.patch b/debian/patches/fix-pod-spelling.patch
deleted file mode 100644
index 39dbe05..0000000
--- a/debian/patches/fix-pod-spelling.patch
+++ /dev/null
@@ -1,64 +0,0 @@
-Description: fix POD spelling
-Origin: vendor
-Bug: https://rt.cpan.org/Ticket/Display.html?id=77453
-Forwarded: https://rt.cpan.org/Ticket/Display.html?id=77453
-Author: Jonathan Yu <jawnsy at cpan.org>
-Reviewed-by: gregor herrmann <gregoa at debian.org>
-Last-Update: 2012-05-26
-
---- a/lib/Class/C3.pm
-+++ b/lib/Class/C3.pm
-@@ -44,7 +44,7 @@
- # this:
- #
- #   $MRO{$class} = {
--#      MRO => [ <class precendence list> ],
-+#      MRO => [ <class precedence list> ],
- #      methods => {
- #          orig => <original location of method>,
- #          code => \&<ref to original method>
-@@ -290,13 +290,13 @@
- 
- C3 is the name of an algorithm which aims to provide a sane method resolution order under multiple
- inheritance. It was first introduced in the langauge Dylan (see links in the L<SEE ALSO> section),
--and then later adopted as the prefered MRO (Method Resolution Order) for the new-style classes in
-+and then later adopted as the preferred MRO (Method Resolution Order) for the new-style classes in
- Python 2.3. Most recently it has been adopted as the 'canonical' MRO for Perl 6 classes, and the
- default MRO for Parrot objects as well.
- 
- =head2 How does C3 work.
- 
--C3 works by always preserving local precendence ordering. This essentially means that no class will
-+C3 works by always preserving local precedence ordering. This essentially means that no class will
- appear before any of its subclasses. Take the classic diamond inheritance pattern for instance:
- 
-      <A>
-@@ -350,7 +350,7 @@
- 
- =item B<initialize>
- 
--This B<must be called> to initalize the C3 method dispatch tables, this module B<will not work> if
-+This B<must be called> to initialize the C3 method dispatch tables, this module B<will not work> if
- you do not do this. It is advised to do this as soon as possible B<after> loading any classes which
- use C3. Here is a quick code example:
- 
-@@ -455,7 +455,7 @@
- 
- =item Use of C<SUPER::>.
- 
--The idea of C<SUPER::> under multiple inheritance is ambigious, and generally not recomended anyway.
-+The idea of C<SUPER::> under multiple inheritance is ambiguous, and generally not recomended anyway.
- However, its use in conjuntion with this module is very much not recommended, and in fact very
- discouraged. The recommended approach is to instead use the supplied C<next::method> feature, see
- more details on its usage above.
---- a/lib/Class/C3/next.pm
-+++ b/lib/Class/C3/next.pm
-@@ -83,7 +83,7 @@
- =head1 DESCRIPTION
- 
- This module is used internally by L<Class::C3> when
--neccesary, and shouldn't be used (or required in
-+necessary, and shouldn't be used (or required in
- distribution dependencies) directly.  It
- defines C<next::method>, C<next::can>, and
- C<maybe::next::method> in pure perl.
diff --git a/debian/patches/series b/debian/patches/series
deleted file mode 100644
index 5622f22..0000000
--- a/debian/patches/series
+++ /dev/null
@@ -1 +0,0 @@
-fix-pod-spelling.patch

-- 
Debian packaging of libclass-c3-perl