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

gregoa pushed a commit to branch master
in repository libtest-warn-perl.

commit 3ec3745d0f8e278eb3432a3efa47b46340b0b5cb
Author: gregor herrmann <gre...@debian.org>
Date:   Sun Dec 25 21:08:57 2016 +0100

    Refresh language.patch (offset).
---
 debian/patches/language.patch | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/debian/patches/language.patch b/debian/patches/language.patch
index ed98d63..8cb21ef 100644
--- a/debian/patches/language.patch
+++ b/debian/patches/language.patch
@@ -3,7 +3,7 @@ Bug-Debian: #322351
 Forwarded: https://rt.cpan.org/Ticket/Display.html?id=49519
 Author: Jay Bonci <jaybo...@debian.org>
 Reviewed-by: gregor herrmann <gre...@debian.org>
-Last-Update: 2014-04-06
+Last-Update: 2016-12-25
 
 --- a/Warn.pm
 +++ b/Warn.pm
@@ -28,7 +28,7 @@ Last-Update: 2014-04-06
  you have to write something like:
  C<warning_is {carp "msg"} {carped =E<gt> 'msg'}, "Test for a carped warning">.
  The test will fail if a "normal" warning is found instead of a "carped" one.
-@@ -95,10 +95,10 @@
+@@ -97,10 +97,10 @@
  which in general has the form "WARNING at __FILE__ line __LINE__".
  So you can check for a warning in the file Foo.pm on line 5 with
  C<warning_like {bar()} qr/at Foo.pm line 5/, "Testname">.
@@ -42,7 +42,7 @@ Last-Update: 2014-04-06
  
  You can also write the regexp in a string as "/.../"
  instead of using the qr/.../ syntax.
-@@ -106,7 +106,7 @@
+@@ -108,7 +108,7 @@
  as strings without slashes are reserved for warning categories
  (to match warning categories as can be seen in the perllexwarn man page).
  
@@ -51,7 +51,7 @@ Last-Update: 2014-04-06
  you can test for warnings via C<carp> with:
  C<warning_like {bar()} {carped => qr/bar called too early/i};>
  
-@@ -126,10 +126,10 @@
+@@ -128,10 +128,10 @@
  
  
  Thanks to the grouping in a tree,
@@ -65,7 +65,7 @@ Last-Update: 2014-04-06
  can only be caught in an eval block. So
  
    warning_like {eval q/"$x"; $x;/} 
-@@ -139,9 +139,8 @@
+@@ -141,9 +141,8 @@
  will work,
  while it wouldn't work without the eval.
  
@@ -77,7 +77,7 @@ Last-Update: 2014-04-06
  
  =item warnings_like BLOCK ARRAYREF, TEST_NAME
  
-@@ -161,7 +160,7 @@
+@@ -163,7 +162,7 @@
                   {carped => qr/bar warning/i},
                   'io'
                  ],
@@ -86,7 +86,7 @@ Last-Update: 2014-04-06
  
  =item warnings_exist BLOCK STRING|ARRAYREF, TEST_NAME
  
-@@ -193,19 +192,19 @@
+@@ -195,19 +194,19 @@
  should be done to %warnings_in_category. You should look into perl source to 
check
  how warning is looking exactly.
  
@@ -114,7 +114,7 @@ Last-Update: 2014-04-06
  
  =head1 TODO
  
-@@ -218,7 +217,7 @@
+@@ -220,7 +219,7 @@
  
  =head1 SEE ALSO
  

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

_______________________________________________
Pkg-perl-cvs-commits mailing list
Pkg-perl-cvs-commits@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-perl-cvs-commits

Reply via email to