In perl.git, the branch blead has been updated
<https://perl5.git.perl.org/perl.git/commitdiff/c1c824fc91d679abcbe5f72252ac95924474a9e4?hp=a06de4dcf2448ead9a5f5dbd87366727ebd91aca>
- Log -----------------------------------------------------------------
commit c1c824fc91d679abcbe5f72252ac95924474a9e4
Author: Marco Fontani <mfont...@cpan.org>
Date: Wed Nov 29 18:32:20 2017 +0100
RT#132520: mention it's OK to attach a patch to an RT ticket
... as was the case of my first patch to perl: I tried to find my use
case in perlhack.pod, failed, and "hoped for the best".
With this, perlhack makes clearer that attaching a patch to an already
existing RT ticket is a perfectly valid and accepted use-case for
getting patches into perl - same as using perlbug.
-----------------------------------------------------------------------
Summary of changes:
pod/perlhack.pod | 3 +++
1 file changed, 3 insertions(+)
diff --git a/pod/perlhack.pod b/pod/perlhack.pod
index a676f46afb..75db3e351b 100644
--- a/pod/perlhack.pod
+++ b/pod/perlhack.pod
@@ -219,6 +219,9 @@ email from our ticket tracking system. This email will
give you a
ticket number. Once your patch has made it to the ticket tracking
system, it will also be sent to the perl5-port...@perl.org list.
+If your patch is related to an already-opened ticket you can also
+attach your patch to that ticket, without having to use perlbug.
+
Patches are reviewed and discussed on the p5p list. Simple,
uncontroversial patches will usually be applied without any discussion.
When the patch is applied, the ticket will be updated and you will
--
Perl5 Master Repository
