>> In either case there is never a hole. Each version stores the complete >> ancestry tree it knows, that is the filename and uuid of each version. >> The problem you run into is that you delete and move version files. If >> Monticello cannot find the files that it refers to in its ancestry you >> cannot merge automatically. That's why repositories should strictly be >> read-only. > > I do not really understand how we ended up with holes then.
I guess I will have to explain it on a white-board, but here's another try: The problem is that Monticello cannot find the common ancestor because you deleted it from its repository. To fix the problem you have to find this version and tell Monticello where it can load it from by adding that repository. It is likely that you find the version somewhere on SqueakSource or in some package-cache on your machine. If you can't find the version you have to merge manually. This means you browse the other version or you calculate the changes between your version and the version you want to merge and apply the changes that you think should go in manually one-by-one. Then you 'adopt' that version to the ancestry. Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
