all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: Starting the Emacs 27 release cycle
Date: Sun, 24 Nov 2019 05:36:09 +0200	[thread overview]
Message-ID: <838so6t07q.fsf@gnu.org> (raw)
In-Reply-To: <871rty46x0.fsf@ericabrahamsen.net> (message from Eric Abrahamsen on Sat, 23 Nov 2019 13:30:35 -0800)

> From: Eric Abrahamsen <eric@ericabrahamsen.net>
> Date: Sat, 23 Nov 2019 13:30:35 -0800
> Cc: Lars Ingebrigtsen <larsi@gnus.org>
> 
> A few months ago I made changes to Gnus so that non-ascii group names
> (which used to mostly stay encoded) were mostly decoded. But I preserved
> the original odd encoding in Gnus' persistence files, so that developers
> could move back and forth between Emacs versions.
> 
> For the 27.1 release I'd like to use Gnus' upgrade mechanism to switch
> to properly-encoded persistence files. The mechanism includes a prompt
> to the user, so they'll be aware of what happened, and it will only
> affect Gnus users with non-ascii group names. But it would mean that
> those users couldn't switch back to Emacs 26 without seeing encoding
> weirdness.
> 
> Hope that's okay...

I don't know enough about Gnus to have an opinion about the potential
risks in this change.  So I'll leave it to you, Lars, and the rest of
the Gnus team to make the decision whether this should be in Emacs 27
or not.

Thanks.



  reply	other threads:[~2019-11-24  3:36 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-23 16:59 Starting the Emacs 27 release cycle Eli Zaretskii
2019-11-23 17:25 ` Robert Pluim
2019-11-23 17:41   ` Eli Zaretskii
2019-11-24 16:51     ` Robert Pluim
2019-11-23 20:02 ` Philipp Stephani
2019-11-24  3:30   ` Eli Zaretskii
2019-11-25 21:48     ` Philipp Stephani
2019-11-26 18:09       ` Eli Zaretskii
2019-11-23 21:30 ` Eric Abrahamsen
2019-11-24  3:36   ` Eli Zaretskii [this message]
2019-11-23 23:16 ` Juri Linkov
2019-11-23 23:49   ` Stefan Kangas
2019-11-25 23:03     ` Phil Sainty
2019-11-27 23:50       ` Juri Linkov
2019-11-28  5:55         ` Stefan Kangas
2019-11-28  8:53           ` Robert Pluim
2019-11-28 10:30             ` VanL
2019-11-28 22:42               ` Juri Linkov
2019-11-27 23:47     ` Juri Linkov
2019-11-29  5:21       ` Richard Stallman
2019-11-24  3:39   ` Eli Zaretskii
2019-12-03 16:13 ` Bastien
2019-12-03 16:23   ` Eli Zaretskii
2019-12-03 22:40     ` Bastien
2019-12-03 23:09       ` Juanma Barranquero
2019-12-04  9:53         ` Bastien
2019-12-04 11:01           ` Juanma Barranquero
  -- strict thread matches above, loose matches on Subject: below --
2019-12-23 16:05 Eli Zaretskii
2019-12-23 16:17 ` Alan Mackenzie
2019-12-23 17:26 ` Pankaj Jangid
2019-12-23 20:05 ` Eli Zaretskii
2019-12-29 20:17 ` Robert Pluim
2019-12-29 20:22   ` Eli Zaretskii
2019-12-29 21:25     ` Robert Pluim

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=838so6t07q.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=eric@ericabrahamsen.net \
    --cc=larsi@gnus.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 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.