Hi Peter, here is my analysis on DynaCASE-PeterUhnak.147.
When going through the history on git, many of the merges do not register as belonging to the DynaCASE package (a git commit belongs to a package when it modify something inside the package directory or modify the version file, I don't remember which indicator I used...). So, to be able to recover all the parents of DynaCASE-PeterUhnak.147, the algorithm (one) has to go through thoses merges transitively until all the branches it has so followed ends with a commit belonging to DynaCASE. Sometimes, drawing this as a graph in the repository inspector would help immensely... Alex, would you be able to show something with Roassal? It would be really nice to see the overall git history graph overlaid with the graph of the history of the selected package. By the way, if you want to explore some of the issues you have to tackle when reading metadata in a git repository, I suggest trying gitg on the dynacase repository... and wait :) Makes Pharo look like a speedy beast :) Thierry 2015-07-24 11:05 GMT+02:00 Peter Uhnák <i.uh...@gmail.com>: > >>> 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. :) >
