Peter, is this the dynacase at https://github.com/dynacase/dynacase ?
Thierry Le 24/07/2015 02:29, Peter Uhnák a écrit :
On Fri, Jul 24, 2015 at 12:26 AM, Thierry Goubier <thierry.goub...@gmail.com <mailto:thierry.goub...@gmail.com>> wrote: Hi Peter, no, I don't think you fucked up your gitfiletree metadata. But the explanation is a bit complex. First thing is that you are looking at a git generated metadata... So what you're asking for (regenerating from git) is already what you are looking at :) Second is that gitfiletree walks your git log to rebuilt the version history. So, I guess that if you look at your git with something like gitg, you will recognize all the versions coming along the diagram lines. It is linked a bit in the way gitfiletree reads through the merges in the git history. I was surprised by that effect, I had a look and yes, there is a good reason for having this done in that way, even if it is a bit surprising at first. Don't remember the exact reasoning... but it was linked to the way git links commits to directories and how merge points appear. If you want to explore that part of GitFileTree, it is in GitFileTreePackageEntry>>buildInfoWith:startingAt:version:ancestry:. Hmm, I'll look at that but still I think it shows way more than it should. The ghost changes are something else, however. Can you elaborate? Basically Pharo (Monticello Browser/Nautilus) shows that a package has changes... so I look at the changes (to see what I'm committing) and I see things that I've already committed. And if I commit it again, only metadata will change (because it was already committed), but the dirty flag will disappear. I have no idea under what circumstances this happens, I thought that maybe I am in different commit... but monticello browser says that I am at the latest one... So I have yet to tell what is the cause. Peter
