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.
Uko > On 24 Jul 2015, at 02:29, Peter Uhnák <i.uh...@gmail.com> wrote: > > > > 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 > > > > > Thierry > > > Le 23/07/2015 23:49, Peter Uhnák a écrit : > Hi, > > it seems that I managed to completely fuck up my gitfiletree metadata... > > e.g.: > Ancestors: DynaCASE-PeterUhnak.148, DynaCASE-PeterUhnak.93, > DynaCASE-PeterUhnak.144, DynaCASE-PeterUhnak.146, > DynaCASE-PeterUhnak.92, DynaCASE-PeterUhnak.142, > DynaCASE-PeterUhnak.140, DynaCASE-PeterUhnak.138, > DynaCASE-PeterUhnak.139, DynaCASE-bliznjan.127, DynaCASE-PeterUhnak.137, > DynaCASE-PeterUhnak.125, DynaCASE-PeterUhnak.126, DynaCASE-bliznjan.123, > DynaCASE-bliznjan.121, DynaCASE-bliznjan.120, DynaCASE-PeterUhnak.119, > DynaCASE-PeterUhnak.117, DynaCASE-PeterUhnak.115, DynaCASE-bliznjan.113, > DynaCASE-PeterUhnak.111, DynaCASE-PeterUhnak.110, > DynaCASE-PeterUhnak.108, DynaCASE-PeterUhnak.102, DynaCASE-bliznjan.95, > DynaCASE-bliznjan.98, DynaCASE-PeterUhnak.91 > > I am also starting to see a lot of ghost changes etc. > > Now, someone mentioned that it would be possible to delete all the > .version and methodProperties.json and whatnot and generate it directly > from git. > > So my question is, is this possible? If yes, how? If no, what would need > to be done (implemented) to make it so? > > Or at least is it possible to completely regenerate all the metadata > purely from git? (To clean up all the mess until.) > > Peter > > >
