On Thu, Jun 30, 2011 at 1:04 PM, Graham Percival <gra...@percival-music.ca> wrote: >> We used to have this, but it was rather fragile, so it only caught >> compilation errors, and no regtest breakage. > > Catching compilation (make and make doc) errors, and telling us > exactly which commits occurred between the last successful build > and the current failing attempt, would still save on average 5 > hours of developer frustration each month. > (oh, also running make distcheck) > > The sooner we know about breakage, the better.
This was when gub was still in flux, so many compile problems then were actually caused by gub changes. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
