Hi brian, brian d foy wrote: > In previous releases, Rafael synced the perlfaq with blead. The version > in RC1 is pretty old and refers to locations in svn.perl.org that are > now stale. > > I brought this up awhile ago: > > http://www.nntp.perl.org/group/perl.perl5.porters/2009/03/msg145275.html > > Nobody told me to do anything different than what I was already doing, > so the sources are still in my perlfaq repo on Github: > > http://github.com/briandfoy/perlfaq/tree/master > > You should be able to talk the perlfaq* files and drop them into perl's > source. If the new method is for me to make patches against perl, I can > do that too, I guess. It just hasn't been how we've done it before, and > I don't pay that close attention to p5p's schedule. > > I have another set of changes to process, but it's not important that > they get into the next release. If I know a date which they might get > into the next release, I can clear out my perlfaq queue. I guess kind of *right now*. I'm in the process of porting a few of the small changes that have been applied to bleadperl in the meantime to a github fork of your repository. When I'm done, I'll copy those merged files into bleadperl. In the long run, I wonder whether it might be worthwhile to move the faq maintenance back to the core repository. I doubt people would be very opposed to giving you commit access to that (and in github times you could always use your own fork and send pull requests occasionally). Cheers, SteffenThread Previous | Thread Next