From: Stainless Steel Rat <ratinox@peorth.gweep.net>
To: Zhang Wei <id.brep@gmail.com>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Is this patch of gnus/pop3.el reasonable?
Date: Mon, 01 Oct 2007 14:16:33 -0400 [thread overview]
Message-ID: <BF73C20E-90C5-4EEC-863B-C2C04BF3157F@peorth.gweep.net> (raw)
In-Reply-To: <uabr3pcp4.fsf@gmail.com>
On Oct 1, 2007, at 2:32 AM, Zhang Wei wrote:
> The current version of pop3.el is quite different from that of xemacs,
> it still didn't support UIDL command, which is quite urgent to prevent
> gnus from fetching the same message repeatedly while messages are kept
> on the server.
UIDL does not exist in RFC 1460, the spec that was current when I
wrote pop3.el.
I wrote pop3.el because I had a need for it. If you have need of
something new then you should write it. That is part of the nature
of free software.
--
\m/ (--) \m/
next prev parent reply other threads:[~2007-10-01 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 22:38 David Kastrup
2007-09-30 23:01 ` Leo
2007-10-01 0:06 ` Stainless Steel Rat
2007-10-01 6:32 ` Zhang Wei
2007-10-01 18:16 ` Stainless Steel Rat [this message]
2007-10-01 17:40 ` Richard Stallman
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=BF73C20E-90C5-4EEC-863B-C2C04BF3157F@peorth.gweep.net \
--to=ratinox@peorth.gweep.net \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=id.brep@gmail.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 NNTP newsgroup(s).