In perl.git, the branch blead has been updated <http://perl5.git.perl.org/perl.git/commitdiff/c17e15dee34dae6e6d689c296022c7ab3ba40d00?hp=2d1c939235f426134ed666017b45a805e3c553a2>
- Log ----------------------------------------------------------------- commit c17e15dee34dae6e6d689c296022c7ab3ba40d00 Author: Smylers <[email protected]> Date: Thu Sep 5 03:39:33 2013 +0200 When sending an email manually so it can have multiple patches, point out that Mutt can construct the email for you. Obviously this isn't as generally relevant as the rest of the Guide, since patchers will use many different mail clients. But it's a significant boon for those who do use Mutt, and a very short addition to the Guide. Mutt is singled out simply because it has this functionality; I suspect that most other widely used mail clients don't. Committer: Removed trailing whitespace. Applied patch manually because other lines in the file had been rebroken and patch no longer applied cleanly. For: RT #119599 ----------------------------------------------------------------------- Summary of changes: pod/perlhack.pod | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/pod/perlhack.pod b/pod/perlhack.pod index da9d0a3..94fd963 100644 --- a/pod/perlhack.pod +++ b/pod/perlhack.pod @@ -90,7 +90,10 @@ 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. +perlbug-generated file, and attach your patches. If you use Mutt, this +command will do that: + + % mutt -H perlbug.rep -a *.patch =item * Thank you -- Perl5 Master Repository
