emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Max Nikulin <manikulin@gmail.com>,
	emacs-orgmode@gnu.org, Bastien <bzg@gnu.org>
Subject: Re: [PATCH] Delete some Emacs 24 compat code
Date: Thu, 30 Jun 2022 20:11:58 -0700	[thread overview]
Message-ID: <CAJcAo8v+M9fKYx06_bdpAGqst4KA6iD7k359_GR97BKXasrQWQ@mail.gmail.com> (raw)
In-Reply-To: <87sfnlk0tj.fsf@localhost>

i use git version, not elpa, so for me, mailing list could tip me off
as early as possible, but not too early, if it said in email subject
header line that in a known upcoming release, it has been decided that
a specified emacs version will no longer be supported [note: i presume
and hope this would not occur in just a plain git update for such a
thing but would get a release that gets noted in email and get that
advance notice],

then upon seeig such email i can stop pulling from git until i am able
to upgrade emacs.  [lots of stuff takes lots and lots of time for me
in my case]  idk if practical, but just saying what seems like it
would be useful to me.

i would then stay at  something reasonably close to the first release
that does not support that version fo emacs.

On 6/30/22, Ihor Radchenko <yantar92@gmail.com> wrote:
> Samuel Wales <samologist@gmail.com> writes:
>
>> idk about others, but as a luddite follower of bugfix/maint, if
>> poissible and not too annoying to do, i would be interested in
>> knowing, at the email subject header level, that the upcoming
>> bugfix/maint release [state org version number] will not support <=
>> [state emacs version number] so that i can prepare at my glacial
>> luddite pace.  this is probably already done, but making it prominent
>> beforehand might help signal the need for changes with lots of time or
>> simplify git stuff [e.g. pull soon as the last pull and make a note
>> not to pull after that, which prevents the need for figuring out
>> rebasing again].
>
> org.el contains the following:
> ;; Package-Requires: ((emacs "25.1"))
>
> So, if you install Org from ELPA using built-in Emacs package manager,
> Org will fail to install on older Emacs versions (AFAIU). I am not sure
> if package.el if going to fall back to earlier Org version though.
>
> In addition, we might also announce the oldest supported Emacs version
> in https://orgmode.org/Changes.html. Either manually, or as a part of
> some automated release script. Bastien, WDYT?
>
> Best,
> Ihor
>
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com


  reply	other threads:[~2022-07-01  3:12 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30 11:19 [PATCH] Delete some Emacs 24 compat code Stefan Kangas
2022-06-30 13:36 ` Ihor Radchenko
2022-06-30 13:39   ` Ihor Radchenko
2022-06-30 15:25   ` Stefan Kangas
2022-07-02  4:11     ` Ihor Radchenko
2022-06-30 15:25 ` Max Nikulin
2022-06-30 15:47   ` Ihor Radchenko
2022-06-30 22:46     ` Samuel Wales
2022-07-01  2:45       ` Ihor Radchenko
2022-07-01  3:11         ` Samuel Wales [this message]
2022-07-01  4:00           ` Tim Cross
2022-07-01  4:44             ` Samuel Wales
2022-07-17  9:35         ` Bastien Guerry
2022-07-18  1:23           ` Samuel Wales
2022-07-31 12:54           ` Ihor Radchenko
2022-08-08 15:46             ` Bastien
2022-08-08 22:12               ` Tim Cross
2022-08-09  0:41                 ` Bastien
2022-08-10 11:50                   ` Ihor Radchenko
2022-08-11 10:23                     ` Bastien
2022-08-11 11:53                       ` Ihor Radchenko
2022-08-12  6:30                         ` Bastien
2022-08-09 15:58               ` Max Nikulin
2022-08-10  0:06                 ` Tim Cross
2022-08-10  0:59                 ` Tom Gillespie
2022-08-10  1:13                   ` Tim Cross
2022-08-10  4:55                     ` Tom Gillespie
2022-08-10 14:18                       ` Tim Cross
2022-08-11  2:59                         ` Samuel Wales
2022-08-11  5:34                           ` Tim Cross
2022-08-11  5:56                           ` Tim Cross

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJcAo8v+M9fKYx06_bdpAGqst4KA6iD7k359_GR97BKXasrQWQ@mail.gmail.com \
    --to=samologist@gmail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=manikulin@gmail.com \
    --cc=yantar92@gmail.com \
    /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/org-mode.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).