public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: overseers@sourceware.cygnus.com,
	Jason Molenda <jason-swarelist@molenda.com>,
	Chris Faylor <cgf@cygnus.com>, Jim Kingdon <kingdon@panix.com>,
	shebs@shebs.cnchost.com, DJ Delorie <dj@cygnus.com>
Subject: Re: [Fwd: ftp probs]
Date: Wed, 21 Jun 2000 08:30:00 -0000	[thread overview]
Message-ID: <9655.961600732@upchuck> (raw)
Message-ID: <20000621083000.ZwlJtSlb1NJDL9Qzb9aAK-TV-nfSqMW8rKe4Hgq_yTw@z> (raw)
In-Reply-To: <Pine.GSO.4.21.0006211627060.16472-100000@nunki.dbai.tuwien.ac.at>

  In message < Pine.GSO.4.21.0006211627060.16472-100000@nunki.dbai.tuwien.ac.at >
you write:
  > On Wed, 21 Jun 2000, Jason Molenda wrote:
  > > The problem is entirely with gcc/cygwin - reduce the ftp load of those
  > > two (both of which have extensive mirroring networks) and the bandwidth
  > > problems evaporate.
  > 
  > I'm also working on this problem, from the GCC side of things:
  > 
  >  o From our web pages we no longer refer to ftp://gcc.gnu.org when it
  >    comes to snapshots, but only list our mirror sites.
  > 
  >  o Shortly I will do the same for our releases.
  > 
  > Jeff, currently the "new snapshot is now available" mails directly
  > specify "egcs.cygnus.com:/pub/egcs/snapshots/2000-06-19". Would you
  > mind changing that to " http://gcc.gnu.org/snapshots.html "?
  > 
  > As far as I understood DJ's analysis, this alone has the potential
  > to save at least 10% (possibly more) of overall traffic.
I don't mind changing it; however, we need to make it clear to folks not
using web browswers how to get snapshots too.  ie, we need to note at
least one site that can be used via raw ftp.

I don't see how we can do that and list a mirror since the snapshot process
won't know when mirrors have sucked down the latest snapshot.

Suggestions?

jeff

  parent reply	other threads:[~2000-06-21  8:30 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-30  6:08 Stan Shebs
2000-06-20 22:05 ` Stan Shebs
2000-12-30  6:08 ` Jim Kingdon
2000-06-20 22:29   ` Jim Kingdon
2000-12-30  6:08   ` Chris Faylor
2000-06-20 22:38     ` Chris Faylor
2000-12-30  6:08     ` Jason Molenda
2000-06-20 23:57       ` Jason Molenda
2000-12-30  6:08       ` DJ Delorie
2000-06-21  7:54         ` DJ Delorie
2000-12-30  6:08         ` Chris Faylor
2000-06-21  8:00           ` Chris Faylor
2000-12-30  6:08           ` DJ Delorie
2000-06-21  8:19             ` DJ Delorie
2000-12-30  6:08       ` Jason Molenda
2000-06-21  0:09         ` Jason Molenda
2000-12-30  6:08         ` Gerald Pfeifer
2000-06-21  8:11           ` Gerald Pfeifer
2000-12-30  6:08           ` Jeffrey A Law [this message]
2000-06-21  8:30             ` Jeffrey A Law
2000-12-30  6:08             ` DJ Delorie
2000-06-21  8:39               ` DJ Delorie
2000-12-30  6:08             ` Gerald Pfeifer
2000-06-22 14:12               ` Gerald Pfeifer
2000-12-30  6:08           ` DJ Delorie
2000-06-21  8:21             ` DJ Delorie
2000-12-30  6:08         ` DJ Delorie
2000-06-21  7:13           ` DJ Delorie
2000-12-30  6:08     ` DJ Delorie
2000-06-21  7:11       ` DJ Delorie
2000-12-30  6:08 ` Chris Faylor
2000-06-20 22:13   ` Chris Faylor
2000-12-30  6:08   ` Jeffrey A Law
2000-06-21  8:47     ` Jeffrey A Law
2000-12-30  6:08   ` Jim Kingdon
2000-06-20 22:36     ` Jim Kingdon

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=9655.961600732@upchuck \
    --to=law@cygnus.com \
    --cc=cgf@cygnus.com \
    --cc=dj@cygnus.com \
    --cc=jason-swarelist@molenda.com \
    --cc=kingdon@panix.com \
    --cc=overseers@sourceware.cygnus.com \
    --cc=pfeifer@dbai.tuwien.ac.at \
    --cc=shebs@shebs.cnchost.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).