On Sun, Aug 9, 2015 at 8:00 PM, Joost Bremmer <[email protected]> wrote:
> I know it makes no sense why it should, but maybe your commit > 84953afaf0255b746b3f591cf869d530f31b3a09 > made it confused? > Whenever something goes wrong for me with git I always try out a fresh > clone to mess around with so you might want to see if that works as well. I > unfortunately did notice that clones don't retain their subtree > infrastructure though, so that's kind of disappointing (I had to merge your > commit manually). > > Thanks for fanficfare though, didn't know that existed. > > Sincerely, > Joost Bremmer > > "We apologize for the inconvenience" > Nope, a clean clone from an earlier history does exactly the same thing. As for my subtrees -- I don't rejoin them. Maybe if I had, I would either know something weird was going on, or I wouldn't end up with new sha1 histories... Glad you enjoy fanficfare though. :) I pathologically haunt the Mobileread.com forums, so I know a little *too* much about these things. :rofl: (Do note there is a calibre plugin as well, which offers enhanced functionality). -- Eli Schwartz
