I am seeing this bug with:
ruby 1.9.2dev (2009-07-18 trunk 24186) [x86_64-linux] and
Is this a possible regression? Should the bug be reopened? Or, am I
simply doing something wrong?
Keep up to date with Rails on Twitter and This Week in Rails
Policies: Conduct, License, Maintenance, Security, Trademarks