summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSmylers <Smylers@stripey.com>2013-09-04 10:49:41 +0100
committerJames E Keenan <jkeenan@cpan.org>2013-09-05 03:06:01 +0200
commitffcd256f12c9b1e7ed8744323fdd3ccfb8593a6c (patch)
tree5bb04c79068efa373fc5de10584b6979dae247e0
parent7eac65da03a4beb9564e00bcaa3adb660608975f (diff)
downloadperl-ffcd256f12c9b1e7ed8744323fdd3ccfb8593a6c.tar.gz
Have perlbug report version being patched
In the Super Quick Patch Guide, run the perlbug and perl from the working copy that the patch is against, so the bug report contains relevant version and configuration data, rather than that of whichever system perl the reporter happens to have installed. For: RT #119599
-rw-r--r--pod/perlhack.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlhack.pod b/pod/perlhack.pod
index 7194469d0e..5d2dec1e40 100644
--- a/pod/perlhack.pod
+++ b/pod/perlhack.pod
@@ -61,7 +61,7 @@ writes the file as a MIME attachment, and sends it with a meaningful
subject:
% git format-patch -1 --attach
- % perlbug -s "[PATCH] $(git log -1 --oneline HEAD)" -f 0001-*.patch
+ % ./perl -Ilib utils/perlbug -s "[PATCH] $(git log -1 --oneline HEAD)" -f 0001-*.patch
The perlbug program will ask you a few questions about your email
address and the patch you're submitting. Once you've answered them it