From: Jeffrey A Law <law@cygnus.com>
To: Manfred Hollstein <manfred@s-direktnet.de>,
Manfred.Hollstein@ks.sel.alcatel.de
Cc: egcs@cygnus.com
Subject: Re: Mail duplicates - Mailing list performance is very bad!
Date: Mon, 30 Mar 1998 17:28:00 -0000 [thread overview]
Message-ID: <19219.891243689@hurl.cygnus.com> (raw)
In-Reply-To: <13599.18826.212420.102010@slsvhmt>
In message < 13599.18826.212420.102010@slsvhmt >you write:
> The appended email was definitely duplicated here (there were others
> as well).
What I need is the complete headers for the multiple messages,
just pointing out a message that was a duplicate doesn't help
me track the problem down.
> Another problem with the lists is their currently very bad
> performance. I usually have a delay of at least 3(!) days by
Yes we know. We're working on the problem, but a solution is probably
still several weeks away. Until then we're just going to have to live
with it.
jeff
next prev parent reply other threads:[~1998-03-30 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-31 0:46 Manfred Hollstein
1998-03-30 17:28 ` Jeffrey A Law [this message]
1998-03-31 0:20 ` Manfred Hollstein
1998-04-02 11:32 ` Gerald Pfeifer
1998-04-02 9:35 ` Matthew D. Langston
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=19219.891243689@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=Manfred.Hollstein@ks.sel.alcatel.de \
--cc=egcs@cygnus.com \
--cc=manfred@s-direktnet.de \
/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).