Gnus development mailing list
 help / color / mirror / Atom feed
From: Andy Moreton <andrewjmoreton@gmail.com>
To: ding@gnus.org
Subject: Re: Calling for testers: scratch/gnus-decoded branch
Date: Thu, 06 Jun 2019 10:14:26 +0100	[thread overview]
Message-ID: <86zhmvgjnx.fsf@gmail.com> (raw)
In-Reply-To: <875zpsycy4.fsf@ericabrahamsen.net>

On Wed 29 May 2019, Eric Abrahamsen wrote:

> Hello reckless Gnus users!
>
> I'm working on the second half of the refactoring that broke everyone's
> Gnus last time -- changing the hash tables to real hash tables, and
> group names to decoded strings.
>
> In order to prevent a repeat performance of the last patch, I have a)
> been much more careful about testing this one, and b) hope I can talk a
> handful of you into helping me test.
>
> Basically you would check out a local copy of the scratch/gnus-decoded
> branch, run "make" in it, BACK UP YOUR .newsrc.eld FILE, then restart
> Emacs and do what you normally do in Gnus, and see if anything looks
> funny. When you're tired of that, switch back to master, run "make"
> again, and replace your backup .newsrc.eld file.

If this set of changes modifies the file format of .newsrc.eld then you
need a different strategy to ensure that users can continue to use their
gnus data on both old and new gnus.

This will be needed until all major distros have updated to use newer
emacs, and users have also updated (i.e. several years).

While modernizing the codebase is useful and welcome, user data is
important, and users will not thank you for doing a one-way "upgrade"
to their files which prevents them from using an older gnus on a
different machine.

> I'm particularly interested in testing from people who have groups with
> non-ascii names -- that's really the whole crux of this issue.
>
> Remember to back up your .newsrc.eld file! If you forget, it will be
> fixable, but Gnus master won't like the decoded non-ascii group names.

If the file data is not compatible between old and new gnus, then you
must change approach to use a new filename for the new format and allow
users to continue to use the old format on new gnus (for compatibility
with also running older gnus using the same files).

    AndyM




  parent reply	other threads:[~2019-06-06  9:14 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30  0:59 Eric Abrahamsen
2019-06-04  5:24 ` Eric Abrahamsen
2019-06-06  2:38   ` Michael Heerdegen
2019-06-06  2:48     ` Emanuel Berg
2019-06-06 23:07       ` Eric Abrahamsen
2019-06-07  3:24         ` Emanuel Berg
2019-06-07  3:58           ` Eric Abrahamsen
2019-06-07  4:15             ` Emanuel Berg
2019-06-07  5:44               ` Eric Abrahamsen
2019-06-07 15:22                 ` Emanuel Berg
2019-06-07 16:52                   ` Eric Abrahamsen
2019-06-08 21:01                     ` Emanuel Berg
2019-06-06  9:14 ` Andy Moreton [this message]
2019-06-06 23:47   ` Eric Abrahamsen
2019-06-07  9:48     ` Tassilo Horn
2019-06-07 16:46       ` Eric Abrahamsen
2019-06-07 22:41 ` Adam Sjøgren
2019-06-10  4:18   ` Eric Abrahamsen
2019-06-16 13:24     ` Adam Sjøgren
2019-06-16 16:53       ` Eric Abrahamsen
2019-06-16 19:06         ` Adam Sjøgren
2019-06-16 19:45           ` Eric Abrahamsen
2019-06-16 20:01             ` Adam Sjøgren
2019-06-16 20:57               ` Eric Abrahamsen
2019-06-16 21:25                 ` Eric Abrahamsen
2019-07-20  9:22                 ` Adam Sjøgren
2019-07-21  3:19                   ` Eric Abrahamsen
2019-07-21 10:08                     ` Adam Sjøgren
2019-07-22 17:05                       ` Eric Abrahamsen
2019-07-22 17:08                         ` Adam Sjøgren
2019-06-16 19:45           ` Eric Abrahamsen

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=86zhmvgjnx.fsf@gmail.com \
    --to=andrewjmoreton@gmail.com \
    --cc=ding@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.
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).