Hi Rowan, On Fri, Mar 20, 2015 at 8:00 AM, Rowan Collins <rowan.coll...@gmail.com> wrote:
> I had no intention of restricting the discussion in any way, apologies if > it came across that way. > > Perhaps what I should have said is it is not *only* time that is needed - > we need to design the replacement before it's worth even thinking about > deprecating something. > Deprecation is future scope that may be years later if it may. I fully agree. I would like to fix this bug now. Current behavior is very annoying... Regards, -- Yasuo Ohgaki yohg...@ohgaki.net
