On Tue, Jul 12, 2016 at 2:27 AM, Jonathan Griffin <jgrif...@mozilla.com> wrote: > > 2 - people sometimes push to try from bad heads (like a mozilla-inbound push > that will eventually get backed out) > > For 2, making sure you push to try only from the current tip of m-c will > avoid this problem, or using MozReview's autoland to try, which will > automatically do the same thing.
There's a conundrum here: - It's natural to develop against m-i because that's where most people land patches. - But you want to push to try against m-c because that's less likely to have unrelated bustage. I (and plenty of other people, I'm sure) have a script for pushing to try that copies patches from my m-i clone to an m-c clone and then pushes to try from there. Sometimes it fails because the patches don't apply cleanly, whereupon I just push to try from the m-i clone and cross my fingers. It's a hack, but an effective one, but it's a shame that there isn't a simple, shared way of doing this. Nick _______________________________________________ dev-builds mailing list dev-builds@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-builds
