From: Vladimir Volovich <vvv@vvv.vsu.ru>
Subject: Re: bug in pop3.el?
Date: 11 Feb 2000 21:03:46 +0300 [thread overview]
Message-ID: <m34sbfipkt.fsf@vvv.vsu.ru> (raw)
In-Reply-To: Stainless Steel Rat's message of "Mon, 7 Feb 2000 16:39:35 -0500"
"Rat" == Stainless Steel Rat writes:
Rat> Sorry, but sending this to me is not going to get you anywhere,
Rat> because I do not support the code anymore. Bug reports should
Rat> go to the FSF.
OK, i've forwarded my message to news:gnu.emacs.bugs too (but still
got no replies).
BTW, pop3.el seems to be part of gnus --- at least it is distributed
with gnus. So maybe gnus maintainers (i.e. not as wide as FSF) are
responsible for bugs in pop3.el? In this case, could somebody look at
this problem?
And putting an info about maintainers of pop3.el would be a nice
thing, too.
Best regards, -- Vladimir.
next prev parent reply other threads:[~2000-02-11 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-07 9:24 Vladimir Volovich
2000-02-07 21:39 ` Stainless Steel Rat
2000-02-11 18:03 ` Vladimir Volovich [this message]
2000-02-11 19:25 ` François Pinard
2000-02-11 21:30 ` Kai Großjohann
2000-02-11 23:04 ` François Pinard
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=m34sbfipkt.fsf@vvv.vsu.ru \
--to=vvv@vvv.vsu.ru \
/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).