Make the link not a link.

[perl5.git] / pod / perlhack.pod

diff --git a/pod/perlhack.pod b/pod/perlhack.pod
index b2cbcf1..dc3f396 100644 (file)
--- a/pod/perlhack.pod
+++ b/pod/perlhack.pod
@@ -63,18 +63,25 @@ sentence.  For example, "Fixed spelling errors in perlhack.pod".
 The next step is to submit your patch to the Perl core ticket system
 via email.
 
-Assuming your patch consists of a single git commit, the following
-writes the file as a MIME attachment, and sends it with a meaningful
-subject:
+If your changes are in a single git commit, run the following commands
+to generate the patch file and attach it to your bug report:
 
-  % git format-patch -1 --attach
-  % ./perl -Ilib utils/perlbug -s "[PATCH] $(
-        git log -1 --oneline HEAD)" -f 0001-*.patch
+  % git format-patch -1
+  % ./perl -Ilib utils/perlbug -p 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
 will submit your patch via email.
 
+If your changes are in multiple commits, generate a patch file for each
+one and provide them to perlbug's C<-p> option separated by commas:
+
+  % git format-patch -3
+  % ./perl -Ilib utils/perlbug -p 0001-fix1.patch,0002-fix2.patch,\
+  > 0003-fix3.patch
+
+When prompted, pick a subject that summarizes your changes.
+
 =item * Thank you
 
 The porters appreciate the time you spent helping to make Perl better.
@@ -83,7 +90,7 @@ Thank you!
 =item * Next time
 
 The next time you wish to make a patch, you need to start from the
-latest perl in a pristine state. Check you don't have any local changes
+latest perl in a pristine state.  Check you don't have any local changes
 or added files in your perl check-out which you wish to keep, then run
 these commands:
 
@@ -166,7 +173,7 @@ You may access the repository over the web.  This allows you to browse
 the tree, see recent commits, subscribe to RSS feeds for the changes,
 search for particular commits and more.  You may access it at
 L<http://perl5.git.perl.org/perl.git>.  A mirror of the repository is
-found at L<http://github.com/mirrors/perl>.
+found at L<https://github.com/Perl/perl5>.
 
 =head2 Read access via rsync
 
@@ -226,8 +233,9 @@ volunteers, and be polite.
 
 Changes are always applied directly to the main development branch,
 called "blead".  Some patches may be backported to a maintenance
-branch. If you think your patch is appropriate for the maintenance
-branch, please explain why when you submit it.
+branch.  If you think your patch is appropriate for the maintenance
+branch (see L<perlpolicy/MAINTENANCE BRANCHES>), please explain why
+when you submit it.
 
 =head2 Getting your patch accepted