Hi David,
I've sent a patch for this problem via github.
Please check it out.
Thank you,
Nori
On Fri, Jan 14, 2011 at 12:18 PM, Nori Hamamoto wrote:
> Sounds good!!
>
> Nori
>
> On Fri, Jan 14, 2011 at 10:57 AM, David Chelimsky wrote:
>
>> On Jan 14, 2011, at 7:29 AM, Nori Hamamoto wrote:
>>
Sounds good!!
Nori
On Fri, Jan 14, 2011 at 10:57 AM, David Chelimsky wrote:
> On Jan 14, 2011, at 7:29 AM, Nori Hamamoto wrote:
>
> I said I'm using the newest version on the repository, but I mean that the
> newest version of rspec1's repository.
> I didn't try it on rspec2 because according t
On Jan 14, 2011, at 7:29 AM, Nori Hamamoto wrote:
> I said I'm using the newest version on the repository, but I mean that the
> newest version of rspec1's repository.
> I didn't try it on rspec2 because according to rspec2's git repository, it
> doesn't support rails 2 and I'm using rails 2.
>
I said I'm using the newest version on the repository, but I mean that the
newest version of rspec1's repository.
I didn't try it on rspec2 because according to rspec2's git repository, it
doesn't support rails 2 and I'm using rails 2.
Sorry about the lack of the information in my report.
Cheers,
On Jan 14, 2011, at 12:19 AM, Nori Hamamoto wrote:
> Hi there,
>
> I've just started using rspec and rspec-rails (both are the newest version on
> git repository).
> I met some inconsistently behavior on it method and its method.
> The following is the way to reproduce it:
>
> command line:
>
