From: Zhang Wei <id.brep@gmail.com>
To: David Kastrup <dak@gnu.org>
Cc: ratinox@peorth.gweep.net, ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Is this patch of gnus/pop3.el reasonable?
Date: Mon, 01 Oct 2007 14:32:23 +0800 [thread overview]
Message-ID: <uabr3pcp4.fsf@gmail.com> (raw)
In-Reply-To: <85ir5r2302.fsf@lola.goethe.zz> (David Kastrup's message of "Mon\, 01 Oct 2007 00\:38\:05 +0200")
David Kastrup <dak@gnu.org> writes:
> I am currently cleaning through unchecked changes in my Emacs tree. I
> found that I have made the following change, presumably in order to
> stop pop3 fetching from hanging in some cases with a possibly patchy
> pop3 server. Could also be related to coding system translation or
> something.
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.
next prev parent reply other threads:[~2007-10-01 6:32 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 [this message]
2007-10-01 18:16 ` Stainless Steel Rat
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=uabr3pcp4.fsf@gmail.com \
--to=id.brep@gmail.com \
--cc=dak@gnu.org \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=ratinox@peorth.gweep.net \
/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).