[libfile-policy-perl] 07/08: Add a patch to fix two POD typos

[Florian Schlichting]

This is an automated email from the git hooks/post-receive script.

fsfs pushed a commit to branch master
in repository libfile-policy-perl.

commit 7e21bc2ebd7865e07cf35fcb806e20a1a856b127
Author: Florian Schlichting <fsfs at debian.org>
Date:   Fri Nov 25 21:53:32 2016 +0100

    Add a patch to fix two POD typos
---
 debian/patches/pod-spelling.patch | 23 +++++++++++++++++++++++
 debian/patches/series             |  1 +
 2 files changed, 24 insertions(+)

diff --git a/debian/patches/pod-spelling.patch b/debian/patches/pod-spelling.patch
new file mode 100644
index 0000000..7f1109d
--- /dev/null
+++ b/debian/patches/pod-spelling.patch
@@ -0,0 +1,23 @@
+Description: fix typos
+Author: Florian Schlichting <fsfs at debian.org>
+
+--- a/lib/File/Policy.pm
++++ b/lib/File/Policy.pm
+@@ -84,7 +84,7 @@
+ 
+ The motivation behind this module was a standard, flexible approach to allow a site wide file policy to be defined.  This will be most useful in large environments where a few sysadmins are responsible for code written by many other people.  Simply ensuring that submitted code calls check_safe() ensures file access is sane, reducing the amount of effort required to do a security audit.
+ 
+-If your code is not security audit'd, or you are the only developer at your site, this might be overkill. However you may consider it good practise regardless and protection against paths in your code getting corrupted accidently or maliciously in the future.
++If your code is not security audit'd, or you are the only developer at your site, this might be overkill. However you may consider it good practise regardless and protection against paths in your code getting corrupted accidentally or maliciously in the future.
+ 
+ There are two major benefits of using this module.  One, sites that do implement a policy can more easily integrate your code in a standard way.  If you have a file policy at your site, you can apply different policies (via File::Policy::Config) in different environments (production, integration test, development) and the appropriate policy is automatically applied without having to change your code or configs.
+ 
+@@ -118,7 +118,7 @@
+ 
+   cp File/Policy/Default.pm File/Policy/YourPolicy.pm
+   
+-and modify YourPolicy accordingly.  Then, create File/Policy/Config.pm contaning:
++and modify YourPolicy accordingly.  Then, create File/Policy/Config.pm containing:
+ 
+   use constant IMPLEMENTATION => 'YourPolicy';
+ 
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 0000000..ad85da2
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+pod-spelling.patch

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-perl/packages/libfile-policy-perl.git