On Thu, 19 Oct 2006, Michael Schmitz wrote:
> > Another buildd for stable-security seems a good idea, but the problem of
> > peak times remains.
>
> And that's where both improved scheduling and closer coordination would
> help. Meaning I'd appreciate some advance warning if something big comes
> down the pipeline, so we can shunt it to the right machine to deal with
> it.
Are there stats about memory, disk, and CPU usage for the previous build, upon
which you can base decisions about which buildd to use?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
