This is an automated email from the git hooks/post-receive script. gregoa pushed a commit to branch master in repository libanyevent-perl.
commit 699f0b40316a199376bc341337961f9558614a93 Author: gregor herrmann <gre...@debian.org> Date: Tue Sep 12 18:35:55 2017 +0200 Add more fixes to fix-spelling.patch. --- debian/patches/fix-spelling.patch | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) diff --git a/debian/patches/fix-spelling.patch b/debian/patches/fix-spelling.patch index d68c781..3a29d14 100644 --- a/debian/patches/fix-spelling.patch +++ b/debian/patches/fix-spelling.patch @@ -103,6 +103,15 @@ Forwarded: mailto:anyev...@lists.schmorp.de (not latest version) --- a/lib/AnyEvent/Intro.pod +++ b/lib/AnyEvent/Intro.pod +@@ -60,7 +60,7 @@ + The motivation behind these designs is often that a module doesn't want + to depend on some complicated XS-module (Net::IRC), or that it doesn't + want to force the user to use some specific event loop at all (LWP), out +-of fear of severly limiting the usefulness of the module: If your module ++of fear of severely limiting the usefulness of the module: If your module + requires Glib, it will not run in a Tk program. + + L<AnyEvent> solves this dilemma, by B<not> forcing module authors to @@ -573,7 +573,7 @@ my $len = sysread $fh, $response, 1024, length $response; @@ -143,6 +152,24 @@ Forwarded: mailto:anyev...@lists.schmorp.de (not latest version) it, but not others: our $SHELL = AnyEvent::Debug::shell "unix/", "/home/schmorp/shell"; +@@ -84,7 +84,7 @@ + + socat readline,history=.anyevent-history unix:shell + +-Binding on C<127.0.0.1> (or C<::1>) might be a less secure but sitll not ++Binding on C<127.0.0.1> (or C<::1>) might be a less secure but still not + totally insecure (on single-user machines) alternative to let you use + other tools, such as telnet: + +@@ -583,7 +583,7 @@ + + Each object is a relatively standard hash with the following members: + +- type => name of the method used ot create the watcher (e.g. C<io>, C<timer>). ++ type => name of the method used to create the watcher (e.g. C<io>, C<timer>). + w => the actual watcher + rfile => reference to the filename of the file the watcher was created in + line => line number where it was created --- a/lib/AnyEvent/Log.pm +++ b/lib/AnyEvent/Log.pm @@ -1230,7 +1230,7 @@ @@ -154,3 +181,14 @@ Forwarded: mailto:anyev...@lists.schmorp.de (not latest version) multiple times by name within the same log specification. =item a perl package name +--- a/lib/AnyEvent/Impl/IOAsync.pm ++++ b/lib/AnyEvent/Impl/IOAsync.pm +@@ -38,7 +38,7 @@ + choice. + + Note that switching loops while watchers are already initialised can have +-unexpected effects, and is not supported unless you can live witht he ++unexpected effects, and is not supported unless you can live with the + consequences. + + =item $AnyEvent::Impl::IOAsync::LOOP -- Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-perl/packages/libanyevent-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