michaeldv/awesome_print — comment on commit 2ad522d36e81545745770502d03235a5e6f006b2
File:  line 0
By jfelchner:

@michaeldv Unfortunately I tried both of those. I have awesome print cloned from my fork. I reset HEAD to match `michaeldv/awesome_print`'s latest commit. Then I set `gem 'awesome_print', :path => '../awesome_print'` which works just fine for the dozens of gems I've patched in the past. No dice.

I also tried `v1.0.1` and `1.0.1` and got the same result. However they are pointing to the same commit so that's expected.

So what's weird is that I have `v1.0.1` installed in my gems. That one works without an issue. Only when using a cloned repo is there a problem.