developers pulling from the stable tree for their next round of changes. My next thought is just to generate olde-school patches so that the very construction of changesets and the linearization of history happens without the synthetic multiple heads? I'm trying to get to the "KernelPractice" style up flow but with a daemon running tests rather than a human doing rote boring merges... --Doug