The second patch leaves the behavior of the method unchanged by default. A user would need to send the new (last) argument to the method to get the new feature. So the consider-subcategories feature could be added without affecting any users except those users (like me) that actually want to use the consider-subcategories feature.
Rich -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Atsushi Shibata Sent: Wednesday, April 05, 2006 2:55 AM To: Coreblog (English) Subject: RE: [COREblog-en] COREBlog 1.2.5 released! Hi :-). On Tue, 4 Apr 2006 08:28:32 -0700, wrote: > Is there anything that can be done to get the bugfix in > http://www.zope.org/Members/ats/COREBlog/Collector.2003-10-11.2831/120 added > to the distribution? The fix is a straightforward two lines of code. I'm very sorry! I forgot your report. > For that matter, I'd really like to see the feature in > http://www.zope.org/Members/ats/COREBlog/Collector.2003-10-11.2831/121 > added. That's only 18 lines of code and is pretty straightforward too. Sorry again... I don't think majority of COREBlog user want subcategory. But, not so few people wants non-categorized entry. How do you think, audiences :-) ---------------------------------------- Atsushi Shibata (Webcore Corp.) [EMAIL PROTECTED] http://www.webcore.co.jp/ ---------------------------------------- _______________________________________________ COREblog-en mailing list [email protected] http://postaria.com/cgi-bin/mailman/listinfo/coreblog-en Unsubscription writing to [EMAIL PROTECTED] _______________________________________________ COREblog-en mailing list [email protected] http://postaria.com/cgi-bin/mailman/listinfo/coreblog-en Unsubscription writing to [EMAIL PROTECTED]
