Check which versions are bold when you open the package. Because when I use gitfiletree it usually shows me that the latest few versions are not loaded (they are in bold) but I am anyway on the latest one.��As I've said, it shows me that I am on the latest version.
Maybe this happens to you because you load it from github and only after you add gitfiletree? (At least from what I remember what you've shown me (and you are using GitFileTree from MetaRepo30?))Understood. So this means all commits you've done (the -bliznjan) were done with filetree?He suffered through with git on Windows for some time, so maybe the later half?
��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, ...?)
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. :)