In perl.git, the branch blead has been updated

<http://perl5.git.perl.org/perl.git/commitdiff/98f0737d71a92167bf1aace8a8d8411b985e3200?hp=7ab791555672f50a01181f675c399d278879e60e>

- Log -----------------------------------------------------------------
commit 98f0737d71a92167bf1aace8a8d8411b985e3200
Author: Abigail <[email protected]>
Date:   Sun Mar 18 18:26:59 2012 +0100

    Paste in the output of Porting/acknowledgements.pl in pod/perl5159delta.pod

M       pod/perl5159delta.pod

commit 08dc3bc803c7923db799f27c4e5183decbebc2f4
Author: Abigail <[email protected]>
Date:   Sun Mar 18 18:24:23 2012 +0100

    Attempt to find an author if (s)he comes via RT.
    
    In the case of commits, it maybe that the reporter used RT, which results
    in a generic RT email address. Instead of just reporting the author as '!',
    we'll do an attempt to see whether he's named in the AUTHORS file.

M       Porting/checkAUTHORS.pl

commit 21ffc8459b739cc13a32f22a2edb7be485a062e0
Author: Abigail <[email protected]>
Date:   Sun Mar 18 17:20:03 2012 +0100

    First shot at perl5159delta.pod

M       pod/.gitignore
A       pod/perl5159delta.pod
-----------------------------------------------------------------------

Summary of changes:
 Porting/checkAUTHORS.pl                  |   16 ++++-
 pod/.gitignore                           |    1 -
 pod/{perldelta.pod => perl5159delta.pod} |  104 ++++++++++++++++++++++++------
 3 files changed, 98 insertions(+), 23 deletions(-)
 copy pod/{perldelta.pod => perl5159delta.pod} (73%)

diff --git a/Porting/checkAUTHORS.pl b/Porting/checkAUTHORS.pl
index 6dd7815..ee2594b 100755
--- a/Porting/checkAUTHORS.pl
+++ b/Porting/checkAUTHORS.pl
@@ -329,7 +329,21 @@ sub process {
 sub _raw_address {
     my $addr = shift;
     my $real_name;
-    if ( $addr =~ /<.*>/ ) {
+    if ($addr =~ /(?:\\")?\s*\(via RT\) <perlbug-followup\@perl\.org>$/p) {
+        my $name = ${^PREMATCH};
+        $addr = 'perlbug-followup@perl\.org';
+        #
+        # Try to find the author
+        #
+        while (my ($email, $author_name) = each %authors) {
+            if ($name eq $author_name) {
+                $addr = $email;
+                $real_name = $name;
+                last;
+            }
+        }
+    }
+    elsif ( $addr =~ /<.*>/ ) {
         $addr =~ s/^\s*(.*)\s*<\s*(.*?)\s*>.*$/$2/;
         $real_name = $1;
     }
diff --git a/pod/.gitignore b/pod/.gitignore
index bedcd69..2cac055 100644
--- a/pod/.gitignore
+++ b/pod/.gitignore
@@ -59,7 +59,6 @@
 /roffitall
 
 # generated
-/perl5159delta.pod
 /perlapi.pod
 /perlintern.pod
 *.html
diff --git a/pod/perldelta.pod b/pod/perl5159delta.pod
similarity index 73%
copy from pod/perldelta.pod
copy to pod/perl5159delta.pod
index 3326e71..7aa1a4e 100644
--- a/pod/perldelta.pod
+++ b/pod/perl5159delta.pod
@@ -2,9 +2,6 @@
 
 =head1 NAME
 
-[ this is a template for a new perldelta file. Any text flagged as
-XXX needs to be processed before release. ]
-
 perldelta - what is new for perl v5.15.9
 
 =head1 DESCRIPTION
@@ -18,13 +15,17 @@ L<perl5158delta>, which describes differences between 
5.15.7 and
 
 =head1 Notice
 
-XXX Any important notices here
+This space intentionally left blank.
 
 =head1 Core Enhancements
 
-XXX New core language features go here. Summarise user-visible core language
-enhancements. Particularly prominent performance optimisations could go
-here, but most should go in the L</Performance Enhancements> section.
+=head2 C<< no feature; >> now means reset to default
+
+C<< no feature >> now resets to the default feature set.  To disable all
+features (which is likely to be a pretty special-purpose request, since
+it presumably won't match any named set of semantics) you can now  
+write C<< no feature ':all' >>.
+
 
 [ List each enhancement as a =head2 entry ]
 
@@ -48,24 +49,20 @@ XXX For a release on a stable branch, this section aspires 
to be:
 
 =head1 Deprecations
 
-XXX Any deprecated features, syntax, modules etc. should be listed here.
-In particular, deprecated modules should be listed here even if they are
-listed as an updated module in the L</Modules and Pragmata> section.
+=head2 Literal C<< "{" >> characters in regular expressions.
 
-[ List each deprecation as a =head2 entry ]
+It has been documented that the current plans include requiring a
+literal C<< "{" >> to be escaped: 5.18 will emit deprecation warnings,
+and it will be required in 5.20.
 
 =head1 Performance Enhancements
 
-XXX Changes which enhance performance without changing behaviour go here. There
-may well be none in a stable release.
-
-[ List each enhancement as a =item entry ]
-
 =over 4
 
 =item *
 
-XXX
+Fix a slowdown in freeing nested hashes. This may speedup the exit of 
+certain programs.
 
 =back
 
@@ -160,6 +157,10 @@ include any changes in L<perldiag> that reconcile it to 
the C<C> code.
 =head2 New Diagnostics
 
 XXX Newly added diagnostic messages go here
+=item *
+
+L<lvalue attribute %s already-defined subroutine|perldiag/"lvalue attribute %s 
already-defined subroutine">, which replaces
+C<< lvalue attribute cannot be removed after the subroutine has been defined 
>>.
 
 =head3 New Errors
 
@@ -243,7 +244,7 @@ that they represent may be covered elsewhere.
 
 =item *
 
-F<t/op/require_37033.t> has been added, to test that C<require> always closes
+F<< t/op/require_37033.t>> has been added, to test that C<require> always 
closes
 the file handle that it opens. Previously, it had been leaking the file handle
 if it happened to have file descriptor 0, which would happen if C<require> was
 called (explicitly or implicitly) when C<STDIN> had been closed.
@@ -327,9 +328,46 @@ L</Modules and Pragmata>.
 
 =item *
 
-C<die;> with a non-reference, non-string value in $@ now properly
+I<Takri> is now considered a script that uses two characters. This corrects
+a Unicode 6.1 omission.
+
+=item *
+
+C<< perlfunc.hmtl >> is now being generated again. [perl #107870]
+
+=item *
+
+C<< $$ >> is no longer tainted. Since this value comes directly from
+C<< getpid() >>, it is always safe.
+
+=item *
+
+Fix leaking a file handle. [perl #37033]
+
+=item *
+
+An off-by-one error caused C<< /[:upper:]/ >> and C<< /[:punct:]/ >> to
+unexepectly match characters with code points above 255. This has been
+rectified. [perl 111400].
+
+=item *
+
+C<< (?foo: ...) >> no longer loses passed in character set.
+
+=item *
+
+Allow attributes to set C<< :lvalue >> on a defined sub. [perl 107366].
+
+=item *
+
+C<< die; >> with a non-reference, non-string value in $@ now properly
 propgates that value [perl #111654].
 
+=item *
+
+C<< Term::ReadLine >> now uses AnyEvent instead of Tk for an event loop.
+
+
 =back
 
 =head1 Known Problems
@@ -358,9 +396,33 @@ here.
 
 =head1 Acknowledgements
 
-XXX Generate this with:
+XXX Redo this on 2012-03-20
+
+Perl 5.15.9 represents approximately 4 weeks of development since Perl 5.15.8
+and contains approximately 74,000 lines of changes across 470 files from 23
+authors.
+
+Perl continues to flourish into its third decade thanks to a vibrant community
+of users and developers. The following people are known to have contributed the
+improvements that became Perl 5.15.9:
+
+Aaron Crane, Abigail, Chris 'BinGOs' Williams, Craig A. Berry, Dave Rolsky,
+David Cantrell, David Golden, David Mitchell, Eric Brine, Father Chrysostomos,
+Florian Ragwitz, James E Keenan, Jesse Vincent, Karl Williamson, Marc Green,
+Max Maischein, Nicholas Clark, Pau Amma, Reini Urban, Ricardo Signes, Tony
+Cook, Yves Orton, Zefram.
+
+The list above is almost certainly incomplete as it is automatically generated
+from version control history. In particular, it does not include the names of
+the (very much appreciated) contributors who reported issues to the Perl bug
+tracker.
+
+Many of the changes included in this version originated in the CPAN modules
+included in Perl's core. We're grateful to the entire CPAN community for
+helping Perl to flourish.
 
-  perl Porting/acknowledgements.pl v5.15.8..HEAD
+For a more complete list of all of Perl's historical contributors, please see
+the F<AUTHORS> file in the Perl source distribution.
 
 =head1 Reporting Bugs
 

--
Perl5 Master Repository

Reply via email to