public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Jim Meyering <jim@meyering.net>
Cc: overseers@sourceware.org
Subject: Re: high load average -> slow builds
Date: Tue, 15 Jan 2013 21:18:00 -0000	[thread overview]
Message-ID: <20130115211713.GH1374@redhat.com> (raw)
In-Reply-To: <87txqiltrg.fsf@rho.meyering.net>

Hi -

On Tue, Jan 15, 2013 at 09:45:07AM +0100, Jim Meyering wrote:

> [...] But longer term, what's the schedule for the hardware update?

As soon as we have the time to do the job right; sorry, no time fixed.

> [...]
>  8219 bugzilla  25   0 56.0  26:17.24  3.1  506m 502m 3104 R email_in.pl
> [...]

These should be gone.  (There was another mailing-loop in effect that
was corrected with some .qmail-FOO magic.)

- FChE

      parent reply	other threads:[~2013-01-15 21:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-15  8:45 Jim Meyering
2013-01-15 18:25 ` Jonathan Larmour
2013-01-15 18:31   ` Jonathan Larmour
2013-01-15 18:36     ` Daniel Berlin
2013-01-15 21:18 ` Frank Ch. Eigler [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130115211713.GH1374@redhat.com \
    --to=fche@redhat.com \
    --cc=jim@meyering.net \
    --cc=overseers@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).