emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [DEV] Bump Emacs requirement to 24.4?
Date: Sat, 15 Aug 2015 10:30:32 +0200	[thread overview]
Message-ID: <87tws1dkd3.fsf@gmx.us> (raw)
In-Reply-To: 87y4hddl2y.fsf@free.fr

Bastien Guerry <bzg@gnu.org> writes:

> Hi Nicolas,
>
> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
>> Master branch is already 24.3+ (with compilation warnings, 24.4+ without
>> them): I committed "org-lint.el", moved some libraries to lexical
>> binding, etc.
>
> Yes, we should have waited for the decision to be taken for this.
>
>> Is there any reason to avoid requiring at least Emacs 24.3 in
>> development branch?
>
> I don't know, but we have only little information on what impact such
> a change will have.  Our best move for now is to ask on mailing lists,
> collect information, then decide.
>
> Also such a change needs to be advertized correctly, I'd rather have
> it for Org 9.0 -- same for dropping XEmacs compatibility.
>
> We don't need to complete the whole 8.x series and may jump to 9.0
> soonish, but for the time being, I suggest you create a 9.0 branch
> with the 24.3 requirement and changes that cannot go without it.
>
> WDYT?

But then what will master hold and what would be the point of it?  It
sounds like a way to rename "master" to "branch9.0"...

Also, Emacs 24.3 was released in March, 2013.  By the time the next Org is
released, it will be more than 3 years old.

Rasmus


-- 
This message is brought to you by the department of redundant departments

  reply	other threads:[~2015-08-15  8:31 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05 19:39 [DEV] Bump Emacs requirement to 24.4? Nicolas Goaziou
2015-08-05 19:38 ` Kaushal
2015-08-05 21:13 ` Suvayu Ali
2015-08-05 21:51 ` Rasmus
2015-08-06  5:42   ` Robert Klein
2015-08-06  8:03     ` Nicolas Goaziou
2015-08-06  8:23       ` Robert Klein
2015-08-06  8:25       ` Rasmus
2015-08-15  7:21         ` Bastien Guerry
2015-08-15  7:29           ` Nicolas Goaziou
2015-08-15  8:15             ` Bastien Guerry
2015-08-15  8:30               ` Rasmus [this message]
2015-08-15  8:37                 ` Bastien Guerry
2015-08-15  9:51                   ` Nicolas Goaziou
2015-08-15 10:02                   ` Rasmus
2015-08-15 12:14                   ` Robert Horn
2015-08-15  9:37               ` Nicolas Goaziou
2015-08-15 14:23                 ` Bastien Guerry
2015-08-15 19:50                   ` Nicolas Goaziou
2015-08-15 23:30                     ` Bastien
2015-08-16  6:08                       ` Achim Gratz
2015-08-16  8:13                         ` Bastien Guerry
2015-08-16 18:03                           ` Achim Gratz
2015-08-18 23:01               ` Bastien
2015-08-19  5:22                 ` David Engster
2015-08-19  9:52                   ` Bastien
2015-08-19  6:04                 ` Suvayu Ali
2015-08-19  9:40                   ` Bastien
2015-08-19 10:31                     ` Suvayu Ali
2015-08-19 16:11                 ` Achim Gratz
2015-08-19 20:07                 ` Rasmus
2015-08-20 23:02                   ` Bastien
2015-09-16  7:58                     ` Rasmus
2015-08-05 22:22 ` Bastien Guerry
2015-08-06  1:07   ` Nicolas Goaziou
2015-08-15  8:45 ` Achim Gratz
2015-08-15  9:28   ` Nicolas Goaziou

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=87tws1dkd3.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --cc=emacs-orgmode@gnu.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 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).