From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: 22025@debbugs.gnu.org
Subject: bug#22025: Emacs 25 corrupts Emacs 24 .emacs.desktop.
Date: Wed, 02 Dec 2015 15:50:49 +0200 [thread overview]
Message-ID: <83egf5j6x2.fsf@gnu.org> (raw)
In-Reply-To: <20151202112722.GA2318@acm.fritz.box>
> Date: Wed, 2 Dec 2015 11:27:22 +0000
> Cc: 22025@debbugs.gnu.org
> From: Alan Mackenzie <acm@muc.de>
>
> > I think NEWS is the appropriate place to alert them to this.
>
> I'm a bit wary about NEWS. How many people actually read it thoroughly?
> At each new release, I try to read NEWS, but my eyes start glazing over
> before I even get half way through.
If they don't pay attention, they will stay with the old format. Do
they lose much?
> But that aside, how about the following NEWS entry (to be followed by
> actual code)?
LGTM, thanks.
next prev parent reply other threads:[~2015-12-02 13:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 8:38 bug#22025: Emacs 25 corrupts Emacs 24 .emacs.desktop Alan Mackenzie
2015-11-27 9:05 ` Eli Zaretskii
2015-11-27 9:47 ` Alan Mackenzie
2015-11-27 10:23 ` Eli Zaretskii
2015-11-27 11:39 ` Alan Mackenzie
2015-11-27 12:27 ` Andy Moreton
2015-12-01 12:19 ` Alan Mackenzie
2015-12-01 15:43 ` Eli Zaretskii
2015-12-01 17:01 ` Alan Mackenzie
2015-12-01 17:46 ` Drew Adams
2015-12-02 12:35 ` Alan Mackenzie
2015-12-02 14:47 ` Drew Adams
2015-12-01 18:46 ` Eli Zaretskii
2015-12-02 11:27 ` Alan Mackenzie
2015-12-02 13:16 ` Andy Moreton
2015-12-02 13:50 ` Eli Zaretskii [this message]
2015-12-03 8:40 ` Alan Mackenzie
2015-12-03 10:30 ` Eli Zaretskii
2016-01-15 16:18 ` Alan Mackenzie
2016-01-15 18:31 ` Eli Zaretskii
2016-01-18 13:37 ` Alan Mackenzie
[not found] ` <<83mvtrj02w.fsf@gnu.org>
2015-12-03 14:33 ` Drew Adams
2015-12-03 14:57 ` Alan Mackenzie
2015-12-03 15:35 ` Drew Adams
2015-12-03 15:44 ` Alan Mackenzie
2019-09-29 21:17 ` Stefan Kangas
[not found] <<20151127083837.GB1782@acm.fritz.box>
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=83egf5j6x2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22025@debbugs.gnu.org \
--cc=acm@muc.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.