public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Jeffrey A Law <law@cygnus.com>
Cc: overseers@sourceware.cygnus.com
Subject: Re: [Fwd: ftp probs]
Date: Sat, 30 Dec 2000 06:08:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.21.0006222300531.98745-100000@deneb.dbai.tuwien.ac.at> (raw)
In-Reply-To: <9655.961600732@upchuck>

On Wed, 21 Jun 2000, Jeffrey A Law wrote:
>> 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 "?
> 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?

I see three possibilities:

 1. Delaying the announcement by several hours

    This probably is useful in any case, as many folks tend to download
    something immediately once it has been announced; without such a delay
    they definitely will use the main site.

 2. I believe these snapshots are done from cron, so we can (and I'm
    willing to take care of that -- just tell me the day and time) tell
    the folks at ftp.freesoftware.com when to synchronize.

 3. We can check whether the folks there can mirror every hour. If it's
    done properly, a mirror run when there has been no change should be
    cheap, essentially a dir list.

Combining 1. and either one of 2. and 3. seems to make sense. To me at
least! ;-)

Gerald
-- 
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
Have a look at http://petition.eurolinux.org !


WARNING: multiple messages have this Message-ID
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Jeffrey A Law <law@cygnus.com>
Cc: overseers@sourceware.cygnus.com
Subject: Re: [Fwd: ftp probs]
Date: Thu, 22 Jun 2000 14:12:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.21.0006222300531.98745-100000@deneb.dbai.tuwien.ac.at> (raw)
Message-ID: <20000622141200.O0ItRCTp5FckffGSl8zCGqx1XJkb2c1dfJaorJYBhqQ@z> (raw)
In-Reply-To: <9655.961600732@upchuck>

On Wed, 21 Jun 2000, Jeffrey A Law wrote:
>> 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 "?
> 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?

I see three possibilities:

 1. Delaying the announcement by several hours

    This probably is useful in any case, as many folks tend to download
    something immediately once it has been announced; without such a delay
    they definitely will use the main site.

 2. I believe these snapshots are done from cron, so we can (and I'm
    willing to take care of that -- just tell me the day and time) tell
    the folks at ftp.freesoftware.com when to synchronize.

 3. We can check whether the folks there can mirror every hour. If it's
    done properly, a mirror run when there has been no change should be
    cheap, essentially a dir list.

Combining 1. and either one of 2. and 3. seems to make sense. To me at
least! ;-)

Gerald
-- 
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
Have a look at http://petition.eurolinux.org !


  parent reply	other threads:[~2000-12-30  6:08 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
2000-06-21  8:30             ` Jeffrey A Law
2000-12-30  6:08             ` Gerald Pfeifer [this message]
2000-06-22 14:12               ` Gerald Pfeifer
2000-12-30  6:08             ` DJ Delorie
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:11       ` DJ Delorie
2000-12-30  6:08 ` Chris Faylor
2000-06-20 22:13   ` Chris Faylor
2000-12-30  6:08   ` Jim Kingdon
2000-06-20 22:36     ` Jim Kingdon
2000-12-30  6:08   ` Jeffrey A Law
2000-06-21  8:47     ` Jeffrey A Law

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=Pine.BSF.4.21.0006222300531.98745-100000@deneb.dbai.tuwien.ac.at \
    --to=pfeifer@dbai.tuwien.ac.at \
    --cc=law@cygnus.com \
    --cc=overseers@sourceware.cygnus.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).