From: Eli Zaretskii <eliz@gnu.org>
To: Sebastian Sturm <s.sturm@arkona-technologies.de>
Cc: emacs-devel@gnu.org
Subject: Re: State of the overlay branch (again)?
Date: Wed, 25 Sep 2019 11:58:45 +0300 [thread overview]
Message-ID: <831rw4oipm.fsf@gnu.org> (raw)
In-Reply-To: <ee052fd5-0057-8eb4-fe17-3fa7e997049f@arkona-technologies.de> (message from Sebastian Sturm on Wed, 25 Sep 2019 09:59:02 +0200)
> From: Sebastian Sturm <s.sturm@arkona-technologies.de>
> Date: Wed, 25 Sep 2019 09:59:02 +0200
>
> Somehow I had thought that the noverlay branch had long since been
> merged with master but when I recently tried to find evidence for that
> merge, I couldn't find any.
>
> So, is the new overlay functionality part of Emacs master (heavily
> renamed perhaps)
No, it wasn't merged.
> or if not, is the merge still planned?
We still hope to merge it at some point.
> If so, is there anything I could do to help speed up the merge
> process (as of yet I don't have any experience with the overlay
> mechanism or Emacs' C internals though)
AFAIK, the work on the branch is not finished, and it is not yet ready
for being merged. So the problem is not the merging itself.
At this point, I also doubt I'd agree to merge it before the emacs-27
branch is cut, as we already have too many potentially destabilizing
changes on master, and adding one more will run the risk of making the
Emacs 27 pretest even longer than I fear it will be.
next prev parent reply other threads:[~2019-09-25 8:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 7:59 State of the overlay branch (again)? Sebastian Sturm
2019-09-25 8:58 ` Eli Zaretskii [this message]
2019-09-25 12:07 ` Sebastian Sturm
2019-09-25 12:32 ` Stefan Monnier
2019-09-25 20:02 ` Sebastian Sturm
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=831rw4oipm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=s.sturm@arkona-technologies.de \
/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.