From 911bfca9fca9e4fddb455137dd35806cfa8adf5a Mon Sep 17 00:00:00 2001 From: Nicholas Clark Date: Thu, 22 Dec 2011 09:23:47 +0100 Subject: [PATCH] Correct the Pod used to block comment a section of git log output. Commit 31940c077ae95db7 added some git log output. To avoid the need to re-indent it, it was "commented out" using Pod. However, the Pod used was buggy. It used a =for, when it should have used a =begin/=end pair. Without this, Pod renderers display the "comment" as if it is part of the documentation, which isn't desired. --- Porting/bisect-runner.pl | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Porting/bisect-runner.pl b/Porting/bisect-runner.pl index 28db89e..92c6852 100755 --- a/Porting/bisect-runner.pl +++ b/Porting/bisect-runner.pl @@ -2476,7 +2476,7 @@ EOPATCH # corrected there. cfgperl (with the fixes) was merged back to blead. # The resultant rather twisty maze of commits looks like this: -=for comment +=begin comment * | | commit 137225782c183172f360c827424b9b9f8adbef0e |\ \ \ Merge: 22c35a8 2a8ee23 @@ -2534,6 +2534,8 @@ EOPATCH | | | | | | p4raw-id: //depot/perl@2133 +=end comment + =cut # and completely confuses git bisect (and at least me), causing it to -- 2.7.4