From: DJ Delorie <dj@delorie.com>
To: law@cygnus.com
Cc: pfeifer@dbai.tuwien.ac.at, overseers@sourceware.cygnus.com,
jason-swarelist@molenda.com, cgf@cygnus.com, kingdon@panix.com,
shebs@shebs.cnchost.com
Subject: Re: [Fwd: ftp probs]
Date: Wed, 21 Jun 2000 08:39:00 -0000 [thread overview]
Message-ID: <200006211539.LAA11439@envy.delorie.com> (raw)
Message-ID: <20000621083900.z1S9RbMI_1Db4PfzmCWmGPYK6rw5fExWuWDCHvaLxnc@z> (raw)
In-Reply-To: <9655.961600732@upchuck>
> 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.
What cygwin does is mention the URL for the mirror sites first, and
then says "or sourceware's heavily overloaded ftp server [here]".
That gives them the option but makes it clear that they should use the
mirrors if possible.
DJGPP's mail says "will be on the mirrors within the next day or so"
but then there is no other way to get DJGPP so they have to wait.
In the cygwin group we've taken the position that people needing
snapshots faster than that should use [incremental] cvs anyway. I
just changed cygwin's snapshot process to run every three days instead
of every day, and we've been reducing the number of stored snapshots
as well. I'll also start switching from gzip to bzip.
next prev parent reply other threads:[~2000-06-21 8:39 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 ` 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
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 ` 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
2000-06-21 8:30 ` Jeffrey A Law
2000-12-30 6:08 ` Gerald Pfeifer
2000-06-22 14:12 ` Gerald Pfeifer
2000-12-30 6:08 ` DJ Delorie [this message]
2000-06-21 8:39 ` DJ Delorie
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: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 ` DJ Delorie
2000-06-21 7:11 ` DJ Delorie
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=200006211539.LAA11439@envy.delorie.com \
--to=dj@delorie.com \
--cc=cgf@cygnus.com \
--cc=jason-swarelist@molenda.com \
--cc=kingdon@panix.com \
--cc=law@cygnus.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).