From: Ari Pollak <aripollak@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel.org has severe performance problems
Date: Thu, 02 Dec 2004 12:47:31 -0500 [thread overview]
Message-ID: <conkfb$t3c$1@sea.gmane.org> (raw)
In-Reply-To: <colqv7$jf4$1@terminus.zytor.com>
I look forward to kernel.org getting better again. Is the source for
diffview.cgi available anywhere on the web so that I can run it locally?
diffview is the only reason I use the main kernel.org site anymore,
since it seems to be the best way to view a whole patch at a glance that
I have found.
H. Peter Anvin wrote:
> Just to let you know; kernel.org has been suffering for performance
> problems lately, but in the last few days, for reasons we're not
> really clear about, the performance problems seem to have spread to
> the upload procedure. Thus, unfortunately, you might see long times
> between uploading something and when things appear on the main
> repository.
>
> We are already in late-stage discussions with sponsors about new
> hardware, so bear with us.
>
> -hpa
next prev parent reply other threads:[~2004-12-02 17:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 1:25 kernel.org has severe performance problems H. Peter Anvin
2004-12-02 17:47 ` Ari Pollak [this message]
2004-12-02 20:38 ` Jan-Benedict Glaw
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='conkfb$t3c$1@sea.gmane.org' \
--to=aripollak@gmail.com \
--cc=linux-kernel@vger.kernel.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