From: Bastien <bzg@gnu.org>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [DEV] Bump Emacs requirement to 24.4?
Date: Wed, 19 Aug 2015 11:40:09 +0200 [thread overview]
Message-ID: <87wpwrr4zq.fsf@gnu.org> (raw)
In-Reply-To: <20150819060459.GC29768@chitra.no-ip.org> (Suvayu Ali's message of "Wed, 19 Aug 2015 08:04:59 +0200")
Hi Suvayu,
Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> I'm slightly confused as-to why this special org-8-master branch is
> needed. As far as I understood from Achim's message (2nd paragraph):
>
> <http://mid.gmane.org/87twrzkbow.fsf@Rainer.invalid>,
>
> that so far maint supports Emacs 23.
Yes, maint supports Emacs 23.
But maint is for minor release, and I want a branch where we can work
on major releases (8.4, 8.5, etc.) that support Emacs 23 too.
The clean way would have been to use drop-emacs23 branch for working
on code that does not support Emacs 23, and continue to use master for
working on major releases, but since nobody wants to revert the code
on master, there is no harm in using "org-8-master" as the new master.
> Although this might have been a
> coincidence, without a conscious decision. It will continue supporting
> Emacs 23 until Org 9. Post Org 9, if required, one can choose to start
> a new maint branch called maint23 for continued Emacs 23 support.
>
> Given the above, I do not understand the need for a separate
> org-8-master branch. Is this a gap in communication, or am I missing
> something here?
I hope my answer clarifies things.
Thanks,
--
Bastien
next prev parent reply other threads:[~2015-08-19 9:40 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
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 [this message]
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=87wpwrr4zq.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=fatkasuvayu+linux@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).