summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNicholas Clark <nick@ccl4.org>2011-12-22 09:23:47 +0100
committerNicholas Clark <nick@ccl4.org>2011-12-22 09:23:47 +0100
commit911bfca9fca9e4fddb455137dd35806cfa8adf5a (patch)
treeb1adefe60f05d79cf3909754d9bb92ef7a252dcb
parent48eabb99200aeda63e70ade7e9df4a309f13fe31 (diff)
downloadperl-911bfca9fca9e4fddb455137dd35806cfa8adf5a.tar.gz
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.
-rwxr-xr-xPorting/bisect-runner.pl4
1 files changed, 3 insertions, 1 deletions
diff --git a/Porting/bisect-runner.pl b/Porting/bisect-runner.pl
index 28db89e094..92c6852d31 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