[SCM] Debian packaging of libdevel-nytprof-perl branch, master, updated. 9fa8e443bb3d70bb9c62c0c188ba829c923c0e20

[Alessandro Ghedini]

The following commit has been merged in the master branch:
commit 58d35be15bfaed299921edd49eaff33e97d52d93
Author: Alessandro Ghedini <al3xbio at gmail.com>
Date:   Thu Aug 16 12:41:58 2012 +0200

    Add fix-spelling-errors.patch

diff --git a/debian/patches/fix-spelling-errors.patch b/debian/patches/fix-spelling-errors.patch
new file mode 100644
index 0000000..5cc4393
--- /dev/null
+++ b/debian/patches/fix-spelling-errors.patch
@@ -0,0 +1,27 @@
+Description: Fix spelling errors
+Origin: vendor
+Forwarded: no
+Author: Alessandro Ghedini <ghedo at debian.org>
+Reviewed-by: Alessandro Ghedini <ghedo at debian.org>
+Last-Update: 2012-08-16
+
+--- a/lib/Devel/NYTProf.pm
++++ b/lib/Devel/NYTProf.pm
+@@ -469,7 +469,7 @@
+ less accurate timings.
+ 
+ Most systems have a 0.01 second granularity in the results from the C<times()>
+-sytem call.  With modern processors having multi- gigahertz clocks, 0.01
++system call.  With modern processors having multi- gigahertz clocks, 0.01
+ seconds is like a lifetime. The 'ticks' of this CPU time clock
+ happen so rarely relative to the activity of a most applications that you'd
+ have to run the code for many hours to have any hope of reasonably useful results.
+@@ -1158,7 +1158,7 @@
+ There are two likely causes for this: clock instability, or accumulated timing
+ errors.
+ 
+-Clock instability, if present on your system, is most likely to be noticable on
++Clock instability, if present on your system, is most likely to be noticeable on
+ very small/fast subroutines that are called very few times.
+ 
+ Accumulated timing errors can arise because the subroutine profiler uses
diff --git a/debian/patches/series b/debian/patches/series
index 793b79b..2780823 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
 manpage-section.patch
 usr-share.patch
+fix-spelling-errors.patch

-- 
Debian packaging of libdevel-nytprof-perl