From: Marc Espie <espie@quatramaran.ens.fr>
To: aoliva@redhat.com
Cc: gcc@gcc.gnu.org
Subject: Re: [PATCH] Partial mirror list update
Date: Tue, 04 Jul 2000 15:27:00 -0000 [thread overview]
Message-ID: <200007042226.AAA04732@quatramaran.ens.fr> (raw)
In-Reply-To: <or4s65aimh.fsf@guarana.lsd.ic.unicamp.br>
In article < or4s65aimh.fsf@guarana.lsd.ic.unicamp.br > you write:
>On Jul 4, 2000, Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> wrote:
>
>> Anyway, please go ahead and install your patch (perhaps unifying
>> "released only, no snapshots" and "no snapshots") and feel free
>> to install similiar changes without explicit approval in the future.
>
>Wouldn't it be nice to have two separate sections, one with sites that
>carry releases and snapshots, and another with sites that carry only
>releases?
Yes, I am afraid this is starting to make sense....
I would even say: do we need the sites that carry only the releases ?
After all, gcc is a gnu program, right ? and there are enough gnu mirrors
around the world...
and it's not like there is a shortage of snapshots mirrors yet, but it
is getting fairly harrowing to go through the list to find the genuine
active mirrors.
All in all, I still see the same trend spreading... mirrors have limited
space, stuff is growing, and when the space gets sparse, the `unused,
useless stuff' is always what vanishes first... nightmarish world of
unix ftp servers that only carries 386 binary rpms... :(
next prev parent reply other threads:[~2000-07-04 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-04 9:26 Marc Espie
2000-07-04 9:35 ` Gerald Pfeifer
2000-07-04 10:52 ` Alexandre Oliva
2000-07-04 15:27 ` Marc Espie [this message]
2000-07-04 15:47 ` Gerald Pfeifer
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=200007042226.AAA04732@quatramaran.ens.fr \
--to=espie@quatramaran.ens.fr \
--cc=aoliva@redhat.com \
--cc=gcc@gcc.gnu.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).