Front page | perl.perl5.porters |
Postings from February 2015
On 02/23/2015 11:19 PM, Karl Williamson wrote: > On 02/23/2015 04:57 PM, Steve Hay wrote: >> What is the status of the Encode customization in blead? > > Thanks for reminding me of this. I had completely forgotten. You > spurred me to issue the pull request: > https://github.com/dankogai/p5-encode/pull/36 >> And now merged into Encode by the maintainer, so is pending release >> Porting/Maintainers.pl has this: >> >> 'CUSTOMIZED' => [ >> # Waiting to be merged upstream if it smokes ok: see CPAN >> RT#100347, >> # in particular see khw's comments on that ticket on 21 >> Nov 2014. >> qw( encoding.pm ), >> ], >> >> The change to encoding.pm was this commit: >> >> http://perl5.git.perl.org/perl.git/commit/3e669301f0a6fa34269f0e1eaf1fbbd72cae498a >> >> >> khw's comments on CPAN RT#100347 say: >> >> "I have just pushed to blead commit >> 3e669301f0a6fa34269f0e1eaf1fbbd72cae498a [...] My commit changes >> encoding to be lexically scoped (but STDIN and STDOUT encoding scope >> is unchanged). This should be soaked for a while to let the CPAN >> smokers see if it causes failures there; if so, it may have to be >> reverted. But in the meantime, any Encode release shouldn't include >> it. I'll issue a pull request when we have enough experience to think >> it will stick." >> >> Is it time to send that pull request now, or does this still need >> soaking for longer? I'm just mindful that we're running out of time >> for 5.22 now. >> >Thread Previous