This is an automated email from the git hooks/post-receive script.
kanashiro-guest pushed a commit to branch master
in repository libcgi-xmlapplication-perl.
Author: Lucas Kanashiro <kanashiro.dua...@gmail.com>
Date: Mon Aug 17 08:58:30 2015 -0300
Remove spelling error patch
Upstream already fixed it
debian/changelog | 2 +
debian/patches/01-fix-spelling-error.diff | 166 ------------------------------
debian/patches/series | 1 -
3 files changed, 2 insertions(+), 167 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 644d733..0c22b63 100644
@@ -2,6 +2,8 @@ libcgi-xmlapplication-perl (1.1.4-1) UNRELEASED; urgency=medium
* Team upload.
* Import upstream version 1.1.4
+ * Remove spelling error patch. Upstream already fixed it
-- Lucas Kanashiro <kanashiro.dua...@gmail.com> Mon, 17 Aug 2015 08:51:13
diff --git a/debian/patches/01-fix-spelling-error.diff
deleted file mode 100644
@@ -1,166 +0,0 @@
-Description: fix man page
-Author: Fabrizio Regalli <fab...@fabreg.it>
-Reviewed-by: gregor herrmann <gre...@debian.org>
-@@ -484,7 +484,7 @@
- content deliverment.
- As well CGI::XMLApplication is designed to support project management
--on code level. The class allows to split web applications into several
-+on code level. The class allows one to split web applications into several
- simple parts. Through this most of the code stays simple and easy to
- maintain. Throughout the whole runtime of a script
- CGI::XMLApplication tries to keep the application stable. As well a
-@@ -520,10 +520,10 @@
- or less redundant code. Since most CGI-scripts are waiting for
- B<events>, which is usually the code abstraction of a click of a
- submit button or an image, CGI::XMLApplication implements a simple
--event system, that allows to keep event related code as separated as
-+event system, that allows one to keep event related code as separated as
--Therefore final application class is not ment to have a constructor
-+Therefore final application class is not meant to have a constructor
- anymore. All functionality should be encapsulated into implicit or
- explicit event handlers. Because of a lack in Perl's OO implementation
- the call of a superclass constructor before the current constructor
-@@ -688,7 +688,7 @@
- to any kind of display type, there should be no need to override this
- function. One can pass a context hash or context object, to pass external
- or prefetched information to the application. This context will be
--available and acessable in all events and most extra functions.
-+available and accessible in all events and most extra functions.
- This function does all event and serialization related work. As well
- there is some validation done as well, so catched events, that are not
-@@ -756,8 +756,8 @@
- To make it clear: If CGI::XMLApplication throws a panic, the
- application is broken, not completely implemented or stylesheets are
--missing or broken. Application panics are ment for debugging purposes
--and to avoid I<Internal Server Errors>. They are B<not> ment as a
-+missing or broken. Application panics are meant for debugging purposes
-+and to avoid I<Internal Server Errors>. They are B<not> meant as a
- replacement of a propper error handling!
- But how does CGI::XMLApplication know about the correct event handler?
-@@ -813,7 +813,7 @@
- =item method sendEvent SCALAR
--Sometimes it could be neccessary to send an event by your own (the
-+Sometimes it could be necessary to send an event by your own (the
- script's) initiative. A possible example could be if you don't have
- client input but path_info data, which determinates how the script
- should behave or session information is missing, so the client should
-@@ -875,7 +875,7 @@
- CGI::XMLApplication knows three implicit events which are more or less
- independent to client responses: They are 'init', 'exit', and
- 'default'. These events already exist for any
--CGI::XMLApplication. They need not to be implemented separatly if they
-+CGI::XMLApplication. They need not to be implemented separately if they
- make no sense for the application.
- =over 4
-@@ -896,7 +896,7 @@
- =item event_default
- This event is called as a fallback mechanism if CGI::XMLApplication
--did not receive a stylesheet id by an other event handler; for example
-+did not receive a stylesheet id by another event handler; for example
- if no event matched.
-@@ -994,7 +994,7 @@
- or remove cookies. The keys of the hash must be the same as the named
- parameters of CGI.pm's header method. One does not need to care about
- the output of these headers, this is done by CGI::XMLApplication
- The content type of the returned data is usually not required to be
- set this way, since the XSLT processor knows about the content type,
-@@ -1005,7 +1005,7 @@
- If the B<getStylesheet> is implemented the CGI::XMLApplication will
- assume the returned value either as a filename of a stylesheet or as a
- XML DOM representation of the same. If Stylesheets are stored in a
--file accessable from the , one should set the common path for the
-+file accessible from the , one should set the common path for the
- stylesheets and let B<CGI::XMLApplication> do the parsing job.
- In cases the stylesheet is already present as a string (e.g. as a
-@@ -1018,14 +1018,14 @@
- If none of these stylesheet selectors succeeds the I<Stylesheet
- missing> panic code is thrown. If the parsing of the stylesheet XML
- fails I<Stylesheet not available> is thrown. The latter case will also
--give some informations where the stylesheet selection failed.
-+give some information where the stylesheet selection failed.
- B<selectStylesheet()> has to return a valid path/filename for the
- stylesheet requested.
- =item getXSLTParameter()
--This function allows to pass a set of parameters to XML::LibXSLT's xsl
-+This function allows one to pass a set of parameters to XML::LibXSLT's xsl
- processor. The function needs only to return a hash and does not need
- to encode the parameters.
-@@ -1037,7 +1037,7 @@
- =head2 Flow Control
- Besides the sendEvent() function does CGI::XMLApplication provide to
--other functions that allow to controll the flow of the application.
-+other functions that allow one to controll the flow of the application.
- These two functions are related to the XML serialization and have not
- affect to the event handling.
-@@ -1066,7 +1066,7 @@
- interpreted as just described.
- If an application sets passthru by itself any external 'passthru'
--parameter will be lost. This is usefull if one likes to avoid, someone
-+parameter will be lost. This is useful if one likes to avoid, someone
- can fetch the plain (untransformed) XML Data.
-@@ -1096,14 +1096,14 @@
- This function searches the query string for a parameter with the
- passed name. The implementation is "imagesave" meaning there is no
- change in the code needed, if you switch from input.type=submit to
--input.type=image or vv. The algorithm tests wheter a full name is
-+input.type=image or vv. The algorithm tests whether a full name is
- found in the querystring, if not it tries tests for the name expanded
- by a '.x'. In context of events this function interprets each item
- part in the query string list as an event. Because of that, the
- algorithm returns only the first item matched.
- If you use the event interface on this function, make sure, the
--HTML-forms pass unique events to the script. This is neccessary to
-+HTML-forms pass unique events to the script. This is necessary to
- avoid confusing behaviour.
- This function is used by testEvent() so if it is required to change
-@@ -1114,7 +1114,7 @@
- This a simple error message handler. By default this function will
- print some information to the client where the application
- failed. While development this is a useful feature on production
--system this may pass vunerable informations about the system to the
-+system this may pass vunerable information about the system to the
- outside. To change the default behaviour, one may write his own panic
- method or simply set I<$CGI::XMLApplication::Quiet> to 1. The latter
- still causes the error page but does not send any error message.
-@@ -1174,7 +1174,7 @@
- The getStylesheet() function should return either a filename or a
- stringnyfied XSL-DOM. For the firstcase it can be a restriction to
--return the fully qualified path. The following functions allow to set
-+return the fully qualified path. The following functions allow one to set
- the stylesheetpath systemwide.
- =over 4
diff --git a/debian/patches/series b/debian/patches/series
deleted file mode 100644
@@ -1 +0,0 @@
Alioth's /usr/local/bin/git-commit-notice on
Pkg-perl-cvs-commits mailing list