> > >> Sorry for the lack of support on windows. You'll have to wait for >>> libcgit. >> >> >> Is there an estimated timeline when this will be? (weeks, months, years, >> ...?) >> > > I don't know; the lib has been included in the Pharo vm for a long time, > and I remember talks about having it for Pharo5. Stef, what is the Pharo > consortium plans on that? >
CCed Stef :) ^^ > > >> Yes, this also happens to me, but it is different. >> Actually this is what I was expecting would happen in the issue described >> originally... that when I check changes (and it was already committed) that >> it would just disappear as false positive... but nope, it still claimed >> it's new and only actual git history have shown that it was a false >> positive. >> >> Anyway, it doesn't seem there will be resolution for this until it can be >> reproduced consistently... so I'll try be more observant. :) >> > > Well, it may be an issue in the way diffs are built, so it would be good > to see it confirmed. Thanks for volunteering, by the way :) > As I'm the only one experiencing this apparently, I don't have a choice but to volunteer. :)
