On Mar 24, 2010, at 10:50 PM, Lukas Renggli wrote:
So this is probably a glitch somewhere
I doubt so.
Lukas: I ***KNOW*** how MC branching/merging works. I KNOW IT. Now I'm trying to understand how the moved package could be moved in treated while it should have been to pharo.
I imagine that when you browsed the different repositories you touched the version and Monticello copied it to its cache. So it isn't enough to know how merging exactly works, but you need to know all the exact semantics of each mouse movement in the MC UI :-)
no this has nothing to do with me idiot you moved the package in the wrong repository I trying to understand why one scenario 1 it barks and on scenario 2 it works because this represents a lot of time wasted... And also what is the step in our process that created the hole in the ancestry. Stef