[libanyevent-perl] 06/07: Add more spelling fixes to fix-spelling.patch.
gregor herrmann
gregoa at debian.org
Fri Feb 12 19:17:01 UTC 2016
This is an automated email from the git hooks/post-receive script.
gregoa pushed a commit to branch master
in repository libanyevent-perl.
commit 7bfb69d22c27277b0da429308c1e0c5798add3bf
Author: gregor herrmann <gregoa at debian.org>
Date: Fri Feb 12 20:13:23 2016 +0100
Add more spelling fixes to fix-spelling.patch.
Thanks: lintian.
---
debian/patches/fix-spelling.patch | 62 +++++++++++++++++++++++++++++++++++++--
1 file changed, 60 insertions(+), 2 deletions(-)
diff --git a/debian/patches/fix-spelling.patch b/debian/patches/fix-spelling.patch
index f7c096d..8a71243 100644
--- a/debian/patches/fix-spelling.patch
+++ b/debian/patches/fix-spelling.patch
@@ -2,8 +2,8 @@ Description: Fix a spelling error found by lintian
Origin: vendor
Author: Alessandro Ghedini <al3xbio at gmail.com>
Reviewed-by: Nicholas Bamber <nicholas at periapt.co.uk>
-Last-Update: 2015-12-05
-Forwarded: mailto:anyevent at lists.schmorp.de
+Last-Update: 2016-02-12
+Forwarded: mailto:anyevent at lists.schmorp.de (not lates version)
--- a/lib/AnyEvent.pm
+++ b/lib/AnyEvent.pm
@@ -16,6 +16,15 @@ Forwarded: mailto:anyevent at lists.schmorp.de
C<$AnyEvent::MAX_SIGNAL_LATENCY> - see the L<ENVIRONMENT VARIABLES>
section for details.
+@@ -2174,7 +2174,7 @@
+
+ If this env variable is nonempty, then its contents will be interpreted by
+ C<AnyEvent::Socket::parse_hostport> and C<AnyEvent::Debug::shell> (after
+-replacing every occurance of C<$$> by the process pid). The shell object
++replacing every occurrence of C<$$> by the process pid). The shell object
+ is saved in C<$AnyEvent::Debug::SHELL>.
+
+ This happens when the first watcher is created.
@@ -3010,7 +3010,7 @@
implement some kind of parallel processing is almost certainly doomed.
@@ -36,6 +45,24 @@ Forwarded: mailto:anyevent at lists.schmorp.de
--- a/lib/AnyEvent/Handle.pm
+++ b/lib/AnyEvent/Handle.pm
+@@ -159,7 +159,7 @@
+ =item on_error => $cb->($handle, $fatal, $message)
+
+ This is the error callback, which is called when, well, some error
+-occured, such as not being able to resolve the hostname, failure to
++occurred, such as not being able to resolve the hostname, failure to
+ connect, or a read error.
+
+ Some errors are fatal (which is indicated by C<$fatal> being true). On
+@@ -367,7 +367,7 @@
+ security implications, AnyEvent::Handle sets this flag automatically
+ unless explicitly specified. Note that setting this flag after
+ establishing a connection I<may> be a bit too late (data loss could
+-already have occured on BSD systems), but at least it will protect you
++already have occurred on BSD systems), but at least it will protect you
+ from most attacks.
+
+ =item read_size => <bytes>
@@ -1892,7 +1892,7 @@
dtection, make sure that any non-TLS data doesn't start with the octet 22
(ASCII SYN, 16 hex) or 128-255 (i.e. highest bit set). The checks this
@@ -45,3 +72,34 @@ Forwarded: mailto:anyevent at lists.schmorp.de
This read type does not rely on L<AnyEvent::TLS> (and thus, not on
L<Net::SSLeay>).
+--- a/lib/AnyEvent/TLS.pm
++++ b/lib/AnyEvent/TLS.pm
+@@ -426,7 +426,7 @@
+
+ certificate private key
+ client/server certificate
+- ca 1, signing client/server certficate
++ ca 1, signing client/server certificate
+ ca 2, signing ca 1
+ ...
+
+--- a/lib/AnyEvent/Intro.pod
++++ b/lib/AnyEvent/Intro.pod
+@@ -573,7 +573,7 @@
+ my $len = sysread $fh, $response, 1024, length $response;
+
+ if ($len <= 0) {
+- # we are done, or an error occured, lets ignore the latter
++ # we are done, or an error occurred, lets ignore the latter
+ undef $read_watcher; # no longer interested
+ $cv->send ($response); # send results
+ }
+@@ -1193,7 +1193,7 @@
+ });
+
+ } else {
+- # some error occured, no article data
++ # some error occurred, no article data
+
+ $finish->($status);
+ }
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-perl/packages/libanyevent-perl.git
More information about the Pkg-perl-cvs-commits
mailing list