emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Bithov Vinu <bithov.vinub@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Backwards compatability
Date: Fri, 23 Apr 2021 09:10:40 +0100	[thread overview]
Message-ID: <878s595slb.fsf@ucl.ac.uk> (raw)
In-Reply-To: <df46ea4a506948a89db854e2ae1d35a0@VI1PR0102MB3327.eurprd01.prod.exchangelabs.com> (Bithov Vinu's message of "Thu, 22 Apr 2021 17:41:41 +0000")

On Thursday, 22 Apr 2021 at 17:41, Bithov Vinu wrote:
> Are any measures being done to make org-mode backwards compatible, so

I cannot speak for the "developers" but backwards compatibility is taken
into account at all times, from what I have seen.  This does not mean
that things do not break as otherwise it would be impossible to evolve
org but changes that break compatibility are not done gratuitously.

The same applies to Emacs more generally.

Note that you can always continue running an old(er) version of org (and
Emacs) should you need to.  (Unlike the proprietary world, older
versions are always available.)  This is not ideal, of course, but the
possibility is there.

-- 
: Eric S Fraga via Emacs 28.0.50, Org release_9.4.4-254-g37749c


       reply	other threads:[~2021-04-23  8:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <df46ea4a506948a89db854e2ae1d35a0@VI1PR0102MB3327.eurprd01.prod.exchangelabs.com>
2021-04-23  8:10 ` Eric S Fraga [this message]
2021-04-22 17:41 Backwards compatability Bithov Vinu
2021-04-25  4:39 ` Bastien
2021-04-25 21:00   ` Nick Savage

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=878s595slb.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=bithov.vinub@gmail.com \
    --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).