[SCM] Packaging of padre perl editor branch, master, updated. debian/0.94+dfsg1-2-11-g267616e

[Dominique Dumont]

The following commit has been merged in the master branch:
commit 9663051ddd1dc60d9aeb506acca6cb12dd30eb40
Author: Dominique Dumont <dod at debian.org>
Date:   Sat May 12 12:20:25 2012 +0200

    new patch to fix spellings reported by lintian

diff --git a/debian/patches/fix-spelling b/debian/patches/fix-spelling
new file mode 100644
index 0000000..d3b6209
--- /dev/null
+++ b/debian/patches/fix-spelling
@@ -0,0 +1,54 @@
+--- a/lib/Padre/Config.pm
++++ b/lib/Padre/Config.pm
+@@ -1730,7 +1730,7 @@
+ =head2 Different types of settings
+ 
+ Padre needs to store different settings. Those preferences are stored in
+-different places depending on their impact. But C<Padre::Config> allows to
++different places depending on their impact. But C<Padre::Config> allows one to
+ access them with a unified API (a mutator). Only their declaration differs
+ in the module.
+ 
+--- a/lib/Padre/MIME.pm
++++ b/lib/Padre/MIME.pm
+@@ -382,7 +382,7 @@
+ 
+ This can allow inherited types to gain default access to various resources
+ such as the comment type or syntax highlighting of the supertypes without
+-needing to be implemented seperately, if they are no different from their
++needing to be implemented separately, if they are no different from their
+ supertype in some respect.
+ 
+ =cut
+--- a/lib/Padre/Wx/Role/Idle.pm
++++ b/lib/Padre/Wx/Role/Idle.pm
+@@ -68,7 +68,7 @@
+ Any remaining parameters to C<idle_method> will be passed through as
+ parameters to the specified method call.
+ 
+-Please note that L<Wx::Event> objects B<must not be used> as paramters
++Please note that L<Wx::Event> objects B<must not be used> as parameters
+ to this method. While the Perl level object will survive until idle time,
+ the underlying Wx event structure for the event will no longer exist, and
+ any attempt to call a method on the event object will segfault Perl.
+--- a/lib/Padre/Wx/Role/Main.pm
++++ b/lib/Padre/Wx/Role/Main.pm
+@@ -124,15 +124,15 @@
+ invalidate the painted state of widgets, this results in a global redraw and
+ on the non-double-bufferred Windows platform this causes flickering.
+ 
+-When a piece of code is making very targetted changes to just the graphical
++When a piece of code is making very targeted changes to just the graphical
+ state of the application and will only need an UPDATE lock (i.e. does not need
+ refresh or database locks) the alternative C<lock_update> method provides a
+-convenience for creating a L<Wx::WindowUpdateLocker> independant of the main
++convenience for creating a L<Wx::WindowUpdateLocker> independent of the main
+ locking API.
+ 
+ By using a localised lock and avoiding a global update lock, this should
+ remove global flickering on these changes, and limit flickering to just
+-the element being update, which should be much less noticable.
++the element being update, which should be much less noticeable.
+ 
+ =cut
+ 
diff --git a/debian/patches/series b/debian/patches/series
index f926444..eeb7c6a 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,4 @@
+fix-spelling
 skip-fishy-test
 disable-tcp-server.patch
 example-interpreter.patch

-- 
Packaging of padre perl editor