From: Bastien Guerry <bzg@gnu.org>
To: Robert Horn <rjhorn@alum.mit.edu>
Cc: emacs-orgmode@gnu.org, Phillip Lord <phillip.lord@russet.org.uk>
Subject: Re: org mode moves to GNU emacs core
Date: Tue, 04 Jul 2017 10:01:29 +0200 [thread overview]
Message-ID: <871spwtyue.fsf@bzg.fr> (raw)
In-Reply-To: <m360f9lf2g.fsf@alum.mit.edu> (Robert Horn's message of "Mon, 03 Jul 2017 11:23:35 -0400")
Hi Robert,
first of all, my bad: what I should have said in all these discussion
is that any decision regarding moving Org to Emacs' core won't happen
any time soon (I'd say two or three years).
Keeping Emacs master branch in sync with Org maint branch is not a
problem anymore, so the decision of whether Org should go into Emacs
core will not depend on this.
And by the time the decision will be made, I expect Emacs and Org
release cycles will come close. In other words: when Org will be as
stable as Emacs and when most of Org's development will happen in its
external modules, it will be time to move Org's development to Emacs.
But all this is very hypothetical, right now very much "bikeshed" :)
Best,
--
Bastien
next prev parent reply other threads:[~2017-07-04 8:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 8:02 org mode moves to GNU emacs core Uwe Brauer
2017-06-29 8:50 ` Rasmus
2017-06-29 9:18 ` Uwe Brauer
2017-07-03 7:28 ` Bastien
2017-07-03 8:33 ` Uwe Brauer
2017-07-03 12:52 ` qTim Cross
2017-07-03 14:21 ` Uwe Brauer
2017-07-03 22:13 ` Tim Cross
[not found] ` <WM!dafdc952e01c9db7d6439bb691272a1ba664e1bae5ab4554e86ed6b7dfea8661d8bbaf476f3ba9dbb09c0c663c84ecc2!@mailhub-mx5.ncl.ac.uk>
2017-07-04 10:45 ` Phillip Lord
[not found] ` <WM!be0b82133cf58eecb5726e88694e8427b36d27c5719f4dbc8d7da9ca2db24765a0806a2a785dcaaf4a6d56d6bd773dc0!@mailhub-mx1.ncl.ac.uk>
2017-07-04 10:36 ` Phillip Lord
[not found] ` <f53ab9c6e9a440bbb5d939a425a97b62@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-07-03 8:52 ` Eric S Fraga
2017-07-03 9:20 ` Alan Schmitt
[not found] ` <WM!87da95345c53f08eaef15c5b7433fda36bb968c366f5815f7f948ed74d91e1259bbc88820ebbf91e3556ee6a4a3e9852!@mailhub-mx5.ncl.ac.uk>
2017-07-03 12:10 ` Phillip Lord
2017-07-03 12:40 ` Bastien Guerry
2017-07-03 15:23 ` Robert Horn
2017-07-04 8:01 ` Bastien Guerry [this message]
[not found] ` <WM!e5e8b591af401b295776634cbabb0d1b446d7bb568c1f8abadd4637a576ff78bf92ed6ccedeed082b016a3f6c9ad6c12!@mailhub-mx3.ncl.ac.uk>
2017-07-04 9:59 ` Phillip Lord
[not found] ` <6d3b27a9e0b245a49cffa029d13bbdb9@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-07-03 13:12 ` Eric S Fraga
2017-07-03 13:30 ` Adonay Felipe Nogueira
2017-07-03 16:52 ` Adonay Felipe Nogueira
2017-07-03 17:58 ` Nick Dokos
2017-07-03 19:38 ` Adonay Felipe Nogueira
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=871spwtyue.fsf@bzg.fr \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=phillip.lord@russet.org.uk \
--cc=rjhorn@alum.mit.edu \
/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.