From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Jeffrey A Law <law@cygnus.com>
Cc: egcs@cygnus.com
Subject: Re: Mail list delays
Date: Wed, 15 Apr 1998 19:57:00 -0000 [thread overview]
Message-ID: <Pine.GSO.3.96.980416002548.9634D-100000@alcyone.dbai.tuwien.ac.at> (raw)
In-Reply-To: <23568.892620968@hurl.cygnus.com>
On Wed, 15 Apr 1998, Jeffrey A Law wrote:
> I haven't timed a message recently, but I suspect the multi-day
> delay problem should be much better now.
Yes, it's much better. On the other hand...
Received: from cygnus.com (runyon.cygnus.com [205.180.230.5])
by vexpert.dbai.tuwien.ac.at (8.8.8/8.8.8) with ESMTP id XAA13683;
Wed, 15 Apr 1998 23:54:46 +0200 (MET-DST)
^^^^^^^^^^^^^^^^^^^^
Date: Tue, 14 Apr 1998 12:14:10 +0200 (MET DST)
^^^^^^^^^^^^^^^^^^^^
Subject: include/typeinfo bootstrap failure for current CVS
Message-ID: <Pine.GSO.3.96.980414121220.1519C-100000@alcyone.dbai.tuwien.ac.at>
...and our site is quite well connected, so I would tend to think that
this is not that unusual (though today the delay was sometimes much
less).
> Hopefully the recent changes are enough to keep things from getting too
> bad before we can put the long term fixes in place.
IMHO a delay of 36 hours is quite unfortunate.
In this case, for example, I received at least four or five different
reports describing exactly the same problem between having sent my own
report and receiving it back from the list.
Gerald
PS: Clearly this is not to bash you, Jeff, Cygnus or your admin staff!
--
Gerald Pfeifer (Jerry) Vienna University of Technology
pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
next prev parent reply other threads:[~1998-04-15 19:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-14 23:16 Jeffrey A Law
1998-04-15 19:57 ` Gerald Pfeifer [this message]
1998-04-16 2:26 ` Manfred Hollstein
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.GSO.3.96.980416002548.9634D-100000@alcyone.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=egcs@cygnus.com \
--cc=law@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).