unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-devel@gnu.org
Subject: Re: Require Emacs >=24.3 for next Org versions?
Date: Sun, 16 Aug 2015 08:35:26 +0200	[thread overview]
Message-ID: <87lhdbkafl.fsf@Rainer.invalid> (raw)
In-Reply-To: CAM9Zgm1BC0h+XdTe=xSp0oU4N45zdCbDrmohnxuv-w3-2Tkj0A@mail.gmail.com

Bozhidar Batsov writes:
> Upgrading Emacs is trivial on all platforms and we need to drive
> forward progress. If someone doesn't want to update Emacs they'll
> probably be fine with using an older version of org as well.

Trivial or not, in some environments changing something like Emacs to a
new version still plays out on the scale of several years, not months;
and both the users and the system administrators can't do much about it.
On the other hand they have control over their personal .emacs.d or
site-lisp.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds




  reply	other threads:[~2015-08-16  6:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-15  8:47 Require Emacs >=24.3 for next Org versions? Bastien Guerry
2015-08-15 23:01 ` Richard Stallman
2015-08-16  5:07   ` Andrés Ramírez
2015-08-16  5:38   ` Bozhidar Batsov
2015-08-16  6:35     ` Achim Gratz [this message]
2015-08-16  6:27   ` Achim Gratz
2015-08-16  9:54     ` Artur Malabarba
2015-08-16 13:14       ` Richard Stallman
2015-08-16 13:45         ` David Kastrup
2015-08-16 14:52         ` Artur Malabarba
2015-08-17  5:04           ` Richard Stallman
2015-08-17  5:24       ` Achim Gratz
2015-08-18  3:41         ` Richard Stallman
2015-08-16 13:13     ` Richard Stallman
2015-08-16 13:13     ` Richard Stallman
2015-08-17  2:16 ` Stephen J. Turnbull
2015-08-18 23:09 ` Bastien

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.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87lhdbkafl.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=emacs-devel@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.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).