This is an automated email from the git hooks/post-receive script.

gregoa pushed a commit to branch master
in repository libsah-schemas-rinci-perl.

commit 2fc7104c39bcbcaae5c868b7b925c9b56b930d29
Author: gregor herrmann <gre...@debian.org>
Date:   Mon Dec 26 03:10:53 2016 +0100

    Drop spelling.patch, fixed upstream.
---
 debian/patches/series         |  1 -
 debian/patches/spelling.patch | 40 ----------------------------------------
 2 files changed, 41 deletions(-)

diff --git a/debian/patches/series b/debian/patches/series
deleted file mode 100644
index 5299247..0000000
--- a/debian/patches/series
+++ /dev/null
@@ -1 +0,0 @@
-spelling.patch
diff --git a/debian/patches/spelling.patch b/debian/patches/spelling.patch
deleted file mode 100644
index 8d0f7a5..0000000
--- a/debian/patches/spelling.patch
+++ /dev/null
@@ -1,40 +0,0 @@
-Description: spelling fixes
-Origin: vendor
-Author: gregor herrmann <gre...@debian.org>
-Last-Update: 2016-12-25
-Forwarded: https://rt.cpan.org/Ticket/Display.html?id=119466
-Bug: https://rt.cpan.org/Ticket/Display.html?id=119466
-
---- a/lib/Sah/SchemaR/rinci/function_meta.pm
-+++ b/lib/Sah/SchemaR/rinci/function_meta.pm
-@@ -186,7 +186,7 @@
- 
- This module is automatically generated by Dist::Zilla::Plugin::Sah::Schemas 
during distribution build.
- 
--A Sah::SchemaR::* module is useful if a client wants to quickly lookup the 
base type of a schema wihout having to do any extra resolving. With 
Sah::Schema::*, one might need to do several lookups if a schema is based on 
another schema, and so on. Compare for example L<Sah::Schema::poseven> vs 
L<Sah::SchemaR::poseven>, where in Sah::SchemaR::poseven one can immediately 
get that the base type is C<int>. Currently L<Perinci::Sub::Complete> uses 
Sah::SchemaR::* instead of Sah::Schema::* for [...]
-+A Sah::SchemaR::* module is useful if a client wants to quickly lookup the 
base type of a schema without having to do any extra resolving. With 
Sah::Schema::*, one might need to do several lookups if a schema is based on 
another schema, and so on. Compare for example L<Sah::Schema::poseven> vs 
L<Sah::SchemaR::poseven>, where in Sah::SchemaR::poseven one can immediately 
get that the base type is C<int>. Currently L<Perinci::Sub::Complete> uses 
Sah::SchemaR::* instead of Sah::Schema::* fo [...]
- 
- =head1 HOMEPAGE
- 
---- a/lib/Sah/SchemaR/rinci/meta.pm
-+++ b/lib/Sah/SchemaR/rinci/meta.pm
-@@ -74,7 +74,7 @@
- 
- This module is automatically generated by Dist::Zilla::Plugin::Sah::Schemas 
during distribution build.
- 
--A Sah::SchemaR::* module is useful if a client wants to quickly lookup the 
base type of a schema wihout having to do any extra resolving. With 
Sah::Schema::*, one might need to do several lookups if a schema is based on 
another schema, and so on. Compare for example L<Sah::Schema::poseven> vs 
L<Sah::SchemaR::poseven>, where in Sah::SchemaR::poseven one can immediately 
get that the base type is C<int>. Currently L<Perinci::Sub::Complete> uses 
Sah::SchemaR::* instead of Sah::Schema::* for [...]
-+A Sah::SchemaR::* module is useful if a client wants to quickly lookup the 
base type of a schema without having to do any extra resolving. With 
Sah::Schema::*, one might need to do several lookups if a schema is based on 
another schema, and so on. Compare for example L<Sah::Schema::poseven> vs 
L<Sah::SchemaR::poseven>, where in Sah::SchemaR::poseven one can immediately 
get that the base type is C<int>. Currently L<Perinci::Sub::Complete> uses 
Sah::SchemaR::* instead of Sah::Schema::* fo [...]
- 
- =head1 HOMEPAGE
- 
---- a/lib/Sah/SchemaR/rinci/result_meta.pm
-+++ b/lib/Sah/SchemaR/rinci/result_meta.pm
-@@ -56,7 +56,7 @@
- 
- This module is automatically generated by Dist::Zilla::Plugin::Sah::Schemas 
during distribution build.
- 
--A Sah::SchemaR::* module is useful if a client wants to quickly lookup the 
base type of a schema wihout having to do any extra resolving. With 
Sah::Schema::*, one might need to do several lookups if a schema is based on 
another schema, and so on. Compare for example L<Sah::Schema::poseven> vs 
L<Sah::SchemaR::poseven>, where in Sah::SchemaR::poseven one can immediately 
get that the base type is C<int>. Currently L<Perinci::Sub::Complete> uses 
Sah::SchemaR::* instead of Sah::Schema::* for [...]
-+A Sah::SchemaR::* module is useful if a client wants to quickly lookup the 
base type of a schema without having to do any extra resolving. With 
Sah::Schema::*, one might need to do several lookups if a schema is based on 
another schema, and so on. Compare for example L<Sah::Schema::poseven> vs 
L<Sah::SchemaR::poseven>, where in Sah::SchemaR::poseven one can immediately 
get that the base type is C<int>. Currently L<Perinci::Sub::Complete> uses 
Sah::SchemaR::* instead of Sah::Schema::* fo [...]
- 
- =head1 HOMEPAGE
- 

-- 
Alioth's /usr/local/bin/git-commit-notice on 
/srv/git.debian.org/git/pkg-perl/packages/libsah-schemas-rinci-perl.git

_______________________________________________
Pkg-perl-cvs-commits mailing list
Pkg-perl-cvs-commits@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-perl-cvs-commits

Reply via email to