This is an automated email from the git hooks/post-receive script.
fsfs pushed a commit to branch master
in repository libmail-bulkmail-perl.
commit 6cc25d4181f13d2c254c4b527c24e97475f33604
Author: Florian Schlichting <f...@debian.org>
Date: Tue Nov 22 23:05:58 2016 +0100
Add a patch to fix POD and spelling errors
---
debian/patches/pod-and-spelling.patch | 89 +++++++++++++++++++++++++++++++++++
debian/patches/series | 1 +
2 files changed, 90 insertions(+)
diff --git a/debian/patches/pod-and-spelling.patch
b/debian/patches/pod-and-spelling.patch
new file mode 100644
index 0000000..cf9686f
--- /dev/null
+++ b/debian/patches/pod-and-spelling.patch
@@ -0,0 +1,89 @@
+Description: fix some POD and spelling errors
+Author: Florian Schlichting <f...@debian.org>
+Forwarded: https://rt.cpan.org/Ticket/Display.html?id=118907
+
+--- a/Bulkmail.pm
++++ b/Bulkmail.pm
+@@ -112,7 +112,7 @@
+ =head1 requires
+
+ Perl 5.6.0, Socket
+- (It probaly can get by with less than 5.6.0, but I haven't tested it in such
an environment)
++ (It probably can get by with less than 5.6.0, but I haven't tested it in
such an environment)
+
+ =cut
+
+@@ -142,8 +142,6 @@
+ # for example. ->_From internally stores whatever is accepted by ->From, and
same with the rest of them.
+ # Don't access the ->_ attributes directly, use the wrappers instead.
+
+-=pod
+-
+ =item From
+
+ Stores the From address of this mailing. Must be a valid email address,
unless Trusting is set.
+@@ -376,7 +374,7 @@
+ arrayref of servers.
+
+ Okay, this is the first major change between 2.x and 3.x. 2.x had methods to
connect to one server (->Smtp, ->Port, etc.).
+-3.x doesn't have those, and the relevent things are now in
Mail::Bulkmail::Server, instead it has a list of servers.
++3.x doesn't have those, and the relevant things are now in
Mail::Bulkmail::Server, instead it has a list of servers.
+
+ servers should contain an arrayref of server objects. You can either create
them externally yourself and pass them in in an arrayref,
+
+@@ -573,7 +571,7 @@
+
+ message_from_file allows you to load your message in from a file. If
message_from_file is
+ set to 1, then the value passed to ->Message() will be assumed to be a path
to a file on disk.
+-That file will be openned in read mode (if possible), read in, and stored as
your message. Note
++That file will be opened in read mode (if possible), read in, and stored as
your message. Note
+ that your entire message text will be read into memory - no matter how large
the message may be.
+
+ This is simply a shortcut so that you don't have to open and read in the
message yourself.
+@@ -2536,7 +2534,7 @@
+ work to be done on your part - it won't just be a drop in replacement. And,
depending upon your list and what options you're using, you
+ may or may not see any benefit to upgrading. Read the docs, ask me questions,
and test test test.
+
+-Don't get me wrong, I'm not going to intentially *try* to make things not
backwards compatible, but if I come up with what I think
++Don't get me wrong, I'm not going to intentionally *try* to make things not
backwards compatible, but if I come up with what I think
+ is a better way of doing things, I'm going to go with it. And I don't like to
pollute modules with a lot of cruft bridgeworks for
+ backwards compatibility. This thing is huge enough as is without having to
worry about making sure internal band-aids work.
+
+--- a/Bulkmail/Dynamic.pm
++++ b/Bulkmail/Dynamic.pm
+@@ -1189,7 +1189,7 @@
+
+ MBD002 - no merge_delimiter
+ MBD003 - different number of keys and values
+- MBD004 - cannot bulid merge hash
++ MBD004 - cannot build merge hash
+
+ =cut
+
+--- a/Bulkmail/Object.pm
++++ b/Bulkmail/Object.pm
+@@ -995,7 +995,7 @@
+ =item isa_path
+
+ This is mainly used by the conf reader, but I wanted to make it publicly
accessible. Given a class, it
+-will return an arrayref containing all of the superclasses of that class, in
inheritence order.
++will return an arrayref containing all of the superclasses of that class, in
inheritance order.
+
+ Note that once a path is looked up for a class, it is cached. So if you
dynamically change @ISA, it won't be reflected in the return of isa_path.
+ Obviously, dynamically changing @ISA is frowned upon as a result.
+@@ -1478,4 +1478,3 @@
+ =cut
+
+
+-=cut
+--- a/Bulkmail/Server.pm
++++ b/Bulkmail/Server.pm
+@@ -277,7 +277,7 @@
+
+ =item talk_attempts
+
+-The response codes for SMTP are pretty rigorously defined, which is obviously
very usefull. a 5xy error is permanently fatal.
++The response codes for SMTP are pretty rigorously defined, which is obviously
very useful. a 5xy error is permanently fatal.
+ a 4xy error is temporarily fatal. It is recommended that if a 4xy error is
encountered, that the client (us) should try re-sending
+ the same command again. talk_attempts specifies the number of times to try
resending a command after receiving a 400 level error
+ from the server.
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 0000000..a0cf537
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+pod-and-spelling.patch
--
Alioth's /usr/local/bin/git-commit-notice on
/srv/git.debian.org/git/pkg-perl/packages/libmail-bulkmail-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
