unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: rms@gnu.org
Cc: mdl@alum.mit.edu, eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: Change in rmail-insert-mime-forwarded-message
Date: Mon, 14 Jan 2013 21:13:29 -0500	[thread overview]
Message-ID: <xx38y39os6.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <E1Tusks-0004VH-Cw@fencepost.gnu.org> (Richard Stallman's message of "Mon, 14 Jan 2013 17:43:46 -0500")


So, what, if anything, should be done about this in the emacs-24 branch
(ie for the 24.3 release)?

I haven't seen a recipe for the "accidentally forward your entire
mail file" problem, but if it happens and you don't notice, it's
obviously awful, and much worse than the original issue (#9521).

My inclination is not to backport the subsequent trunk rmail changes to
emacs-24 at this stage, but to revert the 2012-12-29 rmailmm change in
emacs-24 (only). Then at least 24.3 will be no worse than 24.1,2, and
the new stuff can get more testing in trunk.

But I'll defer to you who actually use Rmail.



  reply	other threads:[~2013-01-15  2:13 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-07  2:18 Change in rmail-insert-mime-forwarded-message Richard Stallman
2013-01-07  3:44 ` Eli Zaretskii
2013-01-08  2:11   ` Richard Stallman
2013-01-09 17:15     ` Eli Zaretskii
2013-01-10  6:19       ` Richard Stallman
2013-01-10 19:03         ` Eli Zaretskii
2013-01-07  4:43 ` Mark Lillibridge
2013-01-08  2:11   ` Richard Stallman
2013-01-08  3:57     ` Mark Lillibridge
2013-01-08 10:02       ` Stephen J. Turnbull
2013-01-08 16:32         ` Mark Lillibridge
2013-01-08 18:13           ` Stephen J. Turnbull
2013-01-23  0:32             ` Mark Lillibridge
2013-01-23  6:44               ` Stephen J. Turnbull
2013-01-09 16:43       ` Richard Stallman
2013-01-10 16:53         ` Mark Lillibridge
2013-01-11  4:43           ` Richard Stallman
2013-01-11  8:10             ` Eli Zaretskii
2013-01-11 16:48               ` Mark Lillibridge
2013-01-13 22:43                 ` Richard Stallman
2013-01-14 22:43                   ` Richard Stallman
2013-01-15  2:13                     ` Glenn Morris [this message]
2013-01-15  4:01                       ` Eli Zaretskii
2013-01-15  5:27                       ` Richard Stallman
2013-01-15 16:07                         ` Eli Zaretskii
2013-01-16  0:04                           ` Richard Stallman
2013-01-23  0:40                             ` Mark Lillibridge
2013-01-15 17:29                         ` Glenn Morris
2013-01-16  0:04                           ` Richard Stallman
2013-01-16  1:14                             ` Glenn Morris
2013-01-17  6:26                     ` Mark Lillibridge
2013-01-17 21:04                       ` Richard Stallman
2013-04-01 19:06                         ` Mark Lillibridge

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=xx38y39os6.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mdl@alum.mit.edu \
    --cc=rms@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).