summaryrefslogtreecommitdiff
path: root/pod/perlhack.pod
diff options
context:
space:
mode:
authorSmylers <Smylers@stripey.com>2013-09-04 12:37:36 +0100
committerJames E Keenan <jkeenan@cpan.org>2013-09-05 03:29:50 +0200
commit2d1c939235f426134ed666017b45a805e3c553a2 (patch)
tree3f8e629018b8cdfbae6711bfb41367d35a9b4648 /pod/perlhack.pod
parente99cf3f0a442462e8a131dbeff46317a9a28f1c4 (diff)
downloadperl-2d1c939235f426134ed666017b45a805e3c553a2.tar.gz
Multiple commits in Super Quick Patch Guide
How to use perlbug when a change is a series of commits, not a single commit. This is the advice RJBS gave me over IRC. Including it in the guide should avoid him having to repeat the advice to others. Committer: Added single quotes around one keyboard command. For: RT #119599
Diffstat (limited to 'pod/perlhack.pod')
-rw-r--r--pod/perlhack.pod17
1 files changed, 17 insertions, 0 deletions
diff --git a/pod/perlhack.pod b/pod/perlhack.pod
index b2cbcf1d4a..da9d0a3082 100644
--- a/pod/perlhack.pod
+++ b/pod/perlhack.pod
@@ -75,6 +75,23 @@ 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
will submit your patch via email.
+If your changes are in multiple commits, generate a patch for each of
+them:
+
+ % git format-patch origin/blead --attach
+
+Run perlbug without any attachments:
+
+ % ./perl -Ilib utils/perlbug
+
+Follow the prompts, picking a subject that summarizes your changes
+overall and has "[PATCH]" at the beginning. Describe your changes in the
+editor window that opens. Instead of sending the report, press 'f' to
+save the message to a file, then quit.
+
+Now create an email using the headers and body from the
+perlbug-generated file, and attach your patches.
+
=item * Thank you
The porters appreciate the time you spent helping to make Perl better.