On Mon, Feb 8, 2010 at 11:08 PM, Seth Thomas Rasmussen <[email protected]> wrote: > On Mon, Feb 8, 2010 at 10:43 PM, Seth Thomas Rasmussen > <[email protected]> wrote: >> On Mon, Feb 8, 2010 at 10:34 PM, Seth Thomas Rasmussen >> <[email protected]> wrote: >>> https://gist.github.com/8ff57d691cca6a64a1bc >>> >>> I've done everything I can think of to verify that the string of text >>> being passed to Commit.list_from_string is what I expect, yet the >>> error remains. I'm hoping I'm just too close to this right now or >>> something, because I feel at a complete loss over something that seems >>> like it shouldn't be so mysterious. >>> >>> As a side note, I'm not convinced I'm using existing Grit APIs most >>> effectively, mainly because of that Grit::Git#run patch I made. Any >>> feedback about an alternative approach would be welcome. >> >> I think the sketchy Grit::Git#run patch is totally unecessary, >> actually.. but the same unexpected nil error remains without it. > > I've updated the gist with the simplified patch and a simplified > example from IRB instead of my app log: > > https://gist.github.com/8ff57d691cca6a64a1bc
OK. I've figured it out. `git whatchanged` raw output includes a line after the commit message describing what kind of changes happened to the path in question such as permissions changes, whether the file was added or modified, etc: :100644 100644 ec367c7... 135ede1... M lib/nitgit.rb Commit.list_from_string was not aware of this. Well then.. carry on. -- You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/github?hl=en.
