My patches to perl

During a few last years, a lot of my patches sent to p5p
slipped
through the cracks.  I'm pretty sure that I'm sitting on
tens of
important (and wanted?) patches which are not applied to the
current
tree.

In addition to this, my Perl-TODO-lists have grown to
several hundred
KB.  This includes, for example, optimizations, bug fixes,
and (major)
simplifications of currently-intimidating features (such as
non-trivial pack/unpack and RExen).  While some of these
must have
already been reimplemented by somebody else, my prior
experience
suggests that most of my TODO lists are still applicable.

Unfortunately, nowadays I cannot work on Perl-at-large
without at
least some external support.  Could this stir enough
interest to win
some support?

Thanks,
Ilya

Ilya Zakharevich wrote:
> During a few last years, a lot of my patches sent
> to p5p slipped through the cracks.

It might be helpful if you could provide links to them
from the p5p mailing list archive.


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection
around 
http://mail.yahoo.com 

On Wed, Dec 20, 2006 at 06:07:52PM -0800, Ilya Zakharevich
wrote:
> During a few last years, a lot of my patches sent to
p5p slipped
> through the cracks.  I'm pretty sure that I'm sitting
on tens of
> important (and wanted?) patches which are not applied
to the current
> tree.
> 
> In addition to this, my Perl-TODO-lists have grown to
several hundred
> KB.  This includes, for example, optimizations, bug
fixes, and (major)
> simplifications of currently-intimidating features
(such as
> non-trivial pack/unpack and RExen).  While some of
these must have
> already been reimplemented by somebody else, my prior
experience
> suggests that most of my TODO lists are still
applicable.
> 
> Unfortunately, nowadays I cannot work on Perl-at-large
without at
> least some external support.  Could this stir enough
interest to win
> some support?
> 

I've dug into this a bit with Google, and so far have found 

   http://www.xray.mpe.mpg.de/mailing-l
ists/perl5-porters/2003-09/msg01528.html

The previous mention of the other SelfLoader patch was
discussed by yourself
and Rafael here 

http://group
s.google.com/group/perl.perl5.porters/browse_thread/thread/5
4e34dda7b82bc8e/8f15a35133febc1d?lnk=st&q=%5BPATCH%5D+gr
oup%3Aperl.perl5.porters+author%3AIlya+author%3AZakharevich&
amp;rnum=10#8f15a35133febc1d

but there were some concerns with that patch.

Steve Peters
stevefisharerojo.org

On Thu, Dec 21, 2006 at 12:13:38AM -0600, Steve Peters
wrote:
> > During a few last years, a lot of my patches sent
to p5p slipped
> > through the cracks.  I'm pretty sure that I'm
sitting on tens of
> > important (and wanted?) patches which are not
applied to the current
> > tree.

> I've dug into this a bit with Google, and so far have
found 
> 
>    http://www.xray.mpe.mpg.de/mailing-l
ists/perl5-porters/2003-09/msg01528.html
> 
> The previous mention of the other SelfLoader patch was
discussed by yourself
> and Rafael here 
> 
> http://group
s.google.com/group/perl.perl5.porters/browse_thread/thread/5
4e34dda7b82bc8e/8f15a35133febc1d?lnk=st&q=%5BPATCH%5D+gr
oup%3Aperl.perl5.porters+author%3AIlya+author%3AZakharevich&
amp;rnum=10#8f15a35133febc1d
> 
> but there were some concerns with that patch.

Fortunately, for the last 3 years I preserve (most of?) my
patches to
Perl on my disk (I see 65, but most of them must be
duplicates/obsoletes, or "OS/2-specific"s).  For
the older ones, I
would need to hunt for in my outgoing mail folders, but it
should not
be too hard too.

What is hard is to detect which of them ARE obsolete, which
of them
still apply, and which must be re-merged manually into the
current
state.

Hope this helps,
Ilya