[libsvn-hooks-perl] 01/02: Add spelling-error-in-manpage.patch patch

[Salvatore Bonaccorso]

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

carnil pushed a commit to branch master
in repository libsvn-hooks-perl.

commit 0c0d10b8306d000ba6fe3da7c24e33720060b393
Author: Salvatore Bonaccorso <carnil at debian.org>
Date:   Tue Jul 19 21:21:47 2016 +0200

    Add spelling-error-in-manpage.patch patch
---
 debian/patches/series                          |  1 +
 debian/patches/spelling-error-in-manpage.patch | 72 ++++++++++++++++++++++++++
 2 files changed, 73 insertions(+)

diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 0000000..f7c4b35
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+spelling-error-in-manpage.patch
diff --git a/debian/patches/spelling-error-in-manpage.patch b/debian/patches/spelling-error-in-manpage.patch
new file mode 100644
index 0000000..319d37d
--- /dev/null
+++ b/debian/patches/spelling-error-in-manpage.patch
@@ -0,0 +1,72 @@
+Description: Fix spelling errors in manpage
+Origin: vendor
+Author: Salvatore Bonaccorso <carnil at debian.org>
+Last-Update: 2016-07-19
+
+--- a/lib/SVN/Hooks/CheckJira.pm
++++ b/lib/SVN/Hooks/CheckJira.pm
+@@ -276,7 +276,7 @@ to match against the commit logs in orde
+ issue keys. By default, the JIRA keys are looked for in the whole
+ commit log, which is equivalent to qr/(.*)/. Sometimes this can be
+ suboptimal because the user can introduce in the message some text
+-that inadvertently looks like a JIRA issue key whithout being so. With
++that inadvertently looks like a JIRA issue key without being so. With
+ this argument, the log message is matched against the REGEXP and only
+ the first matched group (i.e., the part of the message captured by the
+ first parenthesis (C<$1>)) is used to look for JIRA issue keys.
+@@ -309,7 +309,7 @@ The available options are the following:
+ 
+ =item projects => 'PROJKEYS'
+ 
+-By default, the commiter can reference any JIRA issue in the commit
++By default, the committer can reference any JIRA issue in the commit
+ log. You can restrict the allowed keys to a set of JIRA projects by
+ specifying a comma-separated list of project keys to this option.
+ 
+@@ -332,8 +332,8 @@ false value to this option.
+ 
+ =item by_assignee => [01]
+ 
+-By default, the commiter can reference any valid JIRA issue. Passing a
+-true value to this option you require that the commiter can only
++By default, the committer can reference any valid JIRA issue. Passing a
++true value to this option you require that the committer can only
+ reference issues to which she is the current assignee.
+ 
+ =item check_one => CODE-REF
+@@ -428,11 +428,11 @@ commit, do this:
+ 
+ The C<'post_action'> pseudo-check can be used to interact with the
+ JIRA server after a successful commit. For instance, you may want to
+-add a comment to each refered issue like this:
++add a comment to each referred issue like this:
+ 
+     # This routine returns a closure that can be passed to
+     # post_action.  The closure receives a string to be added as a
+-    # comment to each issue refered to by the commit message. The
++    # comment to each issue referred to by the commit message. The
+     # commit info can be interpolated inside the comment using the
+     # SVN::Look method names inside angle brackets.
+ 
+--- a/lib/SVN/Hooks/CheckStructure.pm
++++ b/lib/SVN/Hooks/CheckStructure.pm
+@@ -260,7 +260,7 @@ against the STRUCT_DEF.
+ The function returns true if the check succeeds and dies with a proper
+ message otherwise.
+ 
+-The funcion is intended to check paths as they're shown by the 'svn
++The function is intended to check paths as they're shown by the 'svn
+ ls' command, i.e., with no leading slashes and with a trailing slash
+ to indicate directories. The leading slash is assumed if it's missing,
+ but the trailing slash is needed to indicate directories.
+--- a/lib/SVN/Hooks/JiraAcceptance.pm
++++ b/lib/SVN/Hooks/JiraAcceptance.pm
+@@ -180,7 +180,7 @@ rights.
+ By default the JIRA references are looked for in the commit log
+ message as a whole. Sometimes this can be suboptimal because the user
+ can introduce in the message some text that inadvertently looks like a
+-JIRA reference whithout being so.
++JIRA reference without being so.
+ 
+ With this directive, the log message is matched against the REGEXP and
+ only the first group matched (i.e., the part of the message captured

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