From: Jeff Law <law@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: overseers@sourceware.org
Subject: Re: gdb git mirror (http://sourceware.org/git/gdb.git) wedged?
Date: Wed, 06 Mar 2013 16:23:00 -0000 [thread overview]
Message-ID: <51376D92.7030409@redhat.com> (raw)
In-Reply-To: <51376CD9.3040909@redhat.com>
On 03/06/2013 09:20 AM, Pedro Alves wrote:
> It seems updates are happening, though slower than usual.
>
> Overnight yesterday's commits ended up flowing to git,
> and today, I've noticed today's cvs commits taking more
> than usual to end up in git. They're all there now.
>
> Maybe it's just a sourceware.org-is-overloaded issue.
> (I have no shell access to be able to check/see that
> myself.)
Load seems to be in the 16-22 range..
We've had a lot of problems with the box being overloaded lately. There
was supposed to be new hardware, but I'm not sure about the status of
getting those boxes setup.
jeff
next prev parent reply other threads:[~2013-03-06 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 16:20 Pedro Alves
2013-03-06 16:23 ` Jeff Law [this message]
2013-03-06 16:49 ` Pedro Alves
-- strict thread matches above, loose matches on Subject: below --
2013-03-05 18:33 Pedro Alves
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=51376D92.7030409@redhat.com \
--to=law@redhat.com \
--cc=overseers@sourceware.org \
--cc=palves@redhat.com \
/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).