chromatic wrote: > Be careful with the merge, as the changes to Parrot::Embed were wrong. The > branch shouldn't touch Parrot::Embed at all; it has never used morph.
Yeah. The branch was missing your r36515, so the merge ended up reverting it. That's why I ended up backing out the first merge (via the commit you responded to) and redoing the merge by going through the diffs one by one. I'm sitting on the results of that merge due to some bigint failures, I would like to resolve those first before pushing the result to trunk. Thanks for double checking. Mark _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
