On 17 Apr 2009, at 14:56, Tom Stuart wrote:
Can I git-bisect rspec and rspec-rails independently to try to track down the problem, or are there going to be interdependent changes between RSpec versions 1.2.0 and 1.2.1?
I tried this anyway; the bad commit is http://github.com/dchelimsky/rspec-rails/commit/c9abdccedee97217f28e07ec824bb12cda1c9173 .
Cheers, -Tom _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
