From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 12037@debbugs.gnu.org
Subject: bug#12037: rmail-retry-failure
Date: Sun, 29 Jul 2012 21:47:02 -0400 [thread overview]
Message-ID: <E1Svf4Y-0005NY-VF@fencepost.gnu.org> (raw)
In-Reply-To: <83fw8ah4kb.fsf@gnu.org> (message from Eli Zaretskii on Sun, 29 Jul 2012 20:15:16 +0300)
It looks like rmail-retry-failure was never adapted to the Rmail MIME
feature (which replaces the "boundary" with another text).
Yes, I see. I will write something for this.
--
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
Use Ekiga or an ordinary phone call
next prev parent reply other threads:[~2012-07-30 1:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 22:48 bug#12037: rmail-retry-failure Richard Stallman
2012-07-29 17:15 ` Eli Zaretskii
2012-07-30 1:47 ` Richard Stallman [this message]
2012-09-17 17:13 ` Glenn Morris
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1Svf4Y-0005NY-VF@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=12037@debbugs.gnu.org \
--cc=eliz@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).