From: Richard Stallman <rms@gnu.org>
To: David Kastrup <dak@gnu.org>
Cc: ding@gnus.org, emacs-devel@gnu.org, ratinox@peorth.gweep.net
Subject: Re: Is this patch of gnus/pop3.el reasonable?
Date: Mon, 01 Oct 2007 13:40:46 -0400 [thread overview]
Message-ID: <E1IcPGA-0007vh-Lt@fencepost.gnu.org> (raw)
In-Reply-To: <85ir5r2302.fsf@lola.goethe.zz> (message from David Kastrup on Mon, 01 Oct 2007 00:38:05 +0200)
Now the question is whether this is a bad idea to check into upstream.
I can't see that it will affect operation where the server is correct,
and it might avoid hangs where it isn't.
What do you think?
I am no expert on pop3, but if it is supposed to transmit CRLF
and never use just LF, then this can't hurt.
prev parent reply other threads:[~2007-10-01 17:40 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
2007-10-01 17:40 ` Richard Stallman [this message]
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=E1IcPGA-0007vh-Lt@fencepost.gnu.org \
--to=rms@gnu.org \
--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).