On Fri, 2008-06-20 at 17:05 -0400, Diego Novillo wrote: > On Fri, Jun 20, 2008 at 16:56, Kaveh R. GHAZI <[EMAIL PROTECTED]> wrote: > > > That aside, our current policy already allows e.g. not testing java if > > your change is to a part of the compiler that can't possible affect it. > > I didn't make it completely clear, but my suggestion was mostly to > help us middle/back-end hackers.
One practice I've started using is to use two build trees. One I use in my day-to-day work with only the C and C++ front-ends. I have another build tree that has all languages enabled that is built and tested overnight (before I commit). This means my changes get tested better, but without me incurring the build delays. Ben
