Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Calling for testers: scratch/gnus-decoded branch
Date: Fri, 07 Jun 2019 09:46:43 -0700	[thread overview]
Message-ID: <87o939e424.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87ftollo94.fsf@gnu.org>

Tassilo Horn <tsdh@gnu.org> writes:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> However! I do agree that this change should probably use the existing
>> upgrade machinery, which means it would make most sense to hold off
>> until Gnus ups a version tick.
>
> Isn't Gnus a part and only a part of emacs nowadays, i.e., no separate
> repository anywhere?  In that case, I'd say just go ahead in master so
> that it'll hit the masses with Emacs 27.  I don't think many people
> switch from a newer emacs to an older one on one machine [1], or use
> different emacs versions on different machines but sync their
> newsrc.eld.

That's what I assumed.

Gnus is developed inside Emacs but it has its own version numbers,
though I'm not clear how much they're actually used now, apart from
checking if newsrc.eld is out of date, and updating it.

> Bye,
> Tasslio
>         
> [1] Well, except people like us running the git master and have the
> latest release as a fallback.  So probably it would be a good idea to
> make Gnus backup newsrc.eld somewhere...

It would be a bit tricky to just make _one_ backup -- how do I know if
nothing's been backed up yet, or if it's been backed up but the user has
then deleted the backup? I guess I'd still like to use the built-in
upgrading functions -- at the very least it's nice to prompt the user
and let them know that something's happening. Maybe I can just bump the
Gnus version for wherever it's at when Emacs 27 is released.




  reply	other threads:[~2019-06-07 16:46 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
2019-06-06 23:47   ` Eric Abrahamsen
2019-06-07  9:48     ` Tassilo Horn
2019-06-07 16:46       ` Eric Abrahamsen [this message]
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=87o939e424.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).