From: Miles Bader <miles@gnu.org>
Subject: Re: Weird infinite (?) loop when entering newsgroup
Date: Sat, 22 May 2004 11:00:46 +0900 [thread overview]
Message-ID: <87brkhp6ep.fsf@tc-1-100.kawasaki.gol.ne.jp> (raw)
In-Reply-To: <ubrkhicxv.fsf@xpediantsolutions.com>
Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
> Haven't seen anything like this in a long time. Please email the
> .overview file to me.
I sent you the .overview by email, but haven't gotten my BCC yet; let me
know if you _don't_ get it -- I've noticed that lately whenever I send
email with a large attachment, it can take ages to arrive, so I presume
some sort of idiot virus filtering is screwing with things.
Thanks,
-Miles
--
Run away! Run away!
next prev parent reply other threads:[~2004-05-22 2:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-21 22:24 Miles Bader
2004-05-21 23:21 ` Kevin Greiner
2004-05-22 2:00 ` Miles Bader [this message]
2004-06-24 20:57 ` Rob Browning
2004-06-25 4:44 ` Kevin Greiner
2004-06-26 23:47 ` Rob Browning
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=87brkhp6ep.fsf@tc-1-100.kawasaki.gol.ne.jp \
--to=miles@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 NNTP newsgroup(s).