Sylvain Wallez wrote: > So I would like to have it removed. > > Now it was part of the 2.1.7 release, meaning some people may have used > it, despite its weirdness. So I would like to deprecate it at a high > level (i.e. error rather than the standard warning) in 2.1.8 and > completely remove it in 2.2. > > Thoughts? > +1
Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
