Doug Stewart wrote: > Will this be a fix for 2.1 or will it go against an eventual 2.0.2? Personally, I feel that this is serious enough to warrant a 2.0.2. There were some other post-2.0.1 bug fixes that we could roll in with it. -- Dougal Campbell <dougal at gunters.org> http://dougal.gunters.org/