Stas Bekman <[EMAIL PROTECTED]> writes:
We need to figure out how to automate this.
Perhaps this effort would be a good candidate for
a short-lived "pool-scope-2.x-unstable" branch. Since we may need a widespread fix, a few of us can work together on that branch and quickly merge it back to trunk (once everything is sorted out).
You suggest the branch because we aren't sure that's the way we will do it? Or is it because instead of sending patches one can freely commit things and get others the changes right away?
Otherwise what's wrong with gradual changes, starting with APR::Table and moving to other classes and refactoring on the way...
In any case I hope that others will comment on the problem in hand and give their insights on the proposed solutions...
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
