public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Bradford <john@grabjohn.com>
To: Valdis.Kletnieks@vt.edu
Cc: hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: kernel.org frontpage
Date: Wed, 29 Jan 2003 19:54:34 +0000 (GMT)	[thread overview]
Message-ID: <200301291954.h0TJsZcd002358@darkstar.example.net> (raw)
In-Reply-To: <200301291920.h0TJKF4K007454@turing-police.cc.vt.edu> from "Valdis.Kletnieks@vt.edu" at Jan 29, 2003 02:20:15 PM

> 
> --==_Exmh_1523870505P
> Content-Type: text/plain; charset=us-ascii
> 
> On Wed, 29 Jan 2003 19:14:43 GMT, John Bradford said:
> 
> > I see what you mean, but I don't see how it makes it any less useful
> > to have them on the front page - if you download the latest kernel
> > patch from a mirror, you could then just click on the relevant link on
> > the front page of kernel.org - infact, as http access to kernel.org is
> > frequently much slower than ftp, it might actually be very useful,
> > because anybody downloading via http would make two requests, (OK,
> > about 7, because of the images on the front page), instead of about
> > 13, if they traverse each directory to the .sign file.
> 
> I was arguing that they *should* be on the front page, since they *are*
> useful and it *would* lower the number of requests.

Sorry, I'd deleted the original message, and didn't want to break the
thread :-)

John.

  parent reply	other threads:[~2003-01-29 19:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-29  5:40 kernel.org frontpage H. Peter Anvin
2003-01-29  9:47 ` John Bradford
2003-01-29  9:52   ` H. Peter Anvin
2003-01-29 15:09     ` Valdis.Kletnieks
2003-01-29 18:13       ` H. Peter Anvin
2003-01-29 18:36         ` Chris Friesen
2003-01-29 18:55           ` Valdis.Kletnieks
2003-01-29 19:37             ` Russell King
2003-01-29 19:49               ` Valdis.Kletnieks
2003-01-29 19:14       ` John Bradford
2003-01-29 19:20         ` Valdis.Kletnieks
2003-01-29 19:30           ` H. Peter Anvin
2003-01-30 10:55             ` Hans Reiser
2003-01-29 19:54           ` John Bradford [this message]
2003-01-29 19:29         ` H. Peter Anvin
2003-01-29 19:58           ` John Bradford
2003-01-30 20:42     ` Kasper Dupont
2003-01-30 20:44       ` H. Peter Anvin
2003-01-30 20:50       ` John Bradford
     [not found] <200301290947.h0T9lKa9000750@darkstar.example.net.suse.lists.linux.kernel>
     [not found] ` <3E37A46B.4080907@zytor.com.suse.lists.linux.kernel>
     [not found]   ` <200301291509.h0TF9S4K003537@turing-police.cc.vt.edu.suse.lists.linux.kernel>
     [not found]     ` <3E3819CB.2090409@zytor.com.suse.lists.linux.kernel>
     [not found]       ` <3E381F47.8060200@nortelnetworks.com.suse.lists.linux.kernel>
2003-01-29 18:55         ` Andi Kleen

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=200301291954.h0TJsZcd002358@darkstar.example.net \
    --to=john@grabjohn.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=hpa@zytor.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