From: Eli Zaretskii <eliz@gnu.org>
To: Eval EXEC <execvy@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Feedback on scratch/igc Branch
Date: Sun, 08 Sep 2024 08:46:14 +0300 [thread overview]
Message-ID: <86tteqwvdl.fsf@gnu.org> (raw)
In-Reply-To: <875xr6af7q.fsf@gmail.com> (message from Eval EXEC on Sun, 08 Sep 2024 13:26:17 +0800)
> From: Eval EXEC <execvy@gmail.com>
> Date: Sun, 08 Sep 2024 13:26:17 +0800
>
> Thank you for your excellent work on the scratch/igc branch. Over the
> past few days, I have been using this branch extensively for various
> tasks including reading and sending mail with mu4e, programming with
> lsp-mode and rust-analyzer , and managing my notes using org-roam and
> org-journal. I am pleased to report that the scratch/igc branch is
> remarkably stable and performs exceptionally well.
Thanks, this is very good news.
> Could you please share the next steps for the scratch/igc branch?
Keep using the branch on the various platforms and different build
configurations, to reveal the issues that are still left to be handled
and fixed. Also, we need better GC debugging tools and means, to ease
the investigation of problems we bump into.
> Additionally, do you have any estimated timeline for when it will be
> merged into the master branch?
It's IMO too early to talk about landing this on master. We still
have unresolved issues, like what to do with signals delivered to
Emacs when MPS is collecting garbage and the arena is locked. We also
need to decide whether we want to fork MPS and make changes in it on
our own or not.
next prev parent reply other threads:[~2024-09-08 5:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-08 5:26 Feedback on scratch/igc Branch Eval EXEC
2024-09-08 5:46 ` Eli Zaretskii [this message]
2024-10-23 13:22 ` Jean Louis
2024-10-23 17:27 ` Eli Zaretskii
2024-10-23 20:40 ` Jean Louis
2024-10-23 22:17 ` Philip Kaludercic
2024-10-24 19:11 ` Jean Louis
2024-10-24 6:51 ` Eli Zaretskii
2024-10-24 7:46 ` tomas
2024-10-24 19:14 ` Jean Louis
2024-10-24 19:21 ` tomas
2024-10-24 20:26 ` Andreas Schwab
2024-10-25 6:24 ` Eli Zaretskii
2024-10-25 8:06 ` Andreas Schwab
2024-10-25 10:15 ` Eli Zaretskii
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=86tteqwvdl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=execvy@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 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.