All the Perl that's Practical to Extract and Report
use Perl Log In
jonasbn (1153)
reversethis-{gro.napc} {ta} {nbsanoj}
http://e-diot.dk/
AOL IM: BJonasN (Add Buddy, Send Message)
Perl Programmer located in Copenhagen, Denmark. Active member of Copenhagen Perl Mongers.
Author of:
- Business::DK::CPR
- Business::DK::CVR
- Business::DK::PO
- Business::OnlinePayment::CashCow
- Date::Holidays
- Date::Holidays::Abstract
- Date::Holidays::Super
- Date::Pregnancy
- Games::Bingo
- Games::Bingo::Bot
- Games::Bingo::Print
- Module::Info::File
- Module::Template::Setup
- Test::Timer
and maintainer of:
- Tie::Tools
- XML::Conf
- Workflow
Module::Info Patches
I got an answer from the author of Module::Info (Mattia Barbon) today. And as I anticipated he is probably going to reject my patches.
It is only the second time I send a patch to somebody and apparently I had the proces of using diff upside down
So just for the fun of it I have recreated the pathes (following the advice of Mattia) so I at least could get the hang of using diff properly.
I argued why the patches should be applied, but at the same time I understand Mattia and I respect his decision and that he is the author of Module::Info - and I am thankful that he got back to me with feedback.
Well I learned a lot from the proces - and I will propably make patches to modules again if I get the opportunity, but at the same time I have other things on the drawing board so there is no reason to dwell on this.
--Larry Wall in stab.c from the perl source code
patching (Score:3, Interesting)
I seem to remember Schwern [perl.org] offering this up to the highest bidder a few months ago so it could get the attention it deserved. It's mighty cool how it uses B::Utils to parse the opcode tree. I've been meaning to learn more about that for a few months and just haven't found the time somehow. It looks like Mattia has been applying quite a few patches since he took over, so I imagine he has some solid reasons for not applying your patch.
Reply to This