From: Andrea Corallo <acorallo@gnu.org>
To: Pip Cet <pipcet@protonmail.com>
Cc: rms@gnu.org, "Gerd Möllmann" <gerd.moellmann@gmail.com>,
"Helmut Eller" <eller.helmut@gmail.com>,
luangruo@yahoo.com, emacs-devel@gnu.org
Subject: Re: scratch/igc 26ea4b462a0: Fix GTK-related MPS crashes
Date: Mon, 15 Jul 2024 06:24:41 -0400 [thread overview]
Message-ID: <yp1cynfar6e.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <_twmRKk-TKDjWbOWR3-r69gQ5-tYOeML-dLMVImtAVV0-OndYsvlEM-7iqH8cYW81KwIKuDrJimMUdAKjWJtHDHPSjCsWFO22bog4OHRF4U=@protonmail.com> (Pip Cet's message of "Sat, 13 Jul 2024 20:35:37 +0000")
Pip Cet <pipcet@protonmail.com> writes:
> On Thursday, July 11th, 2024 at 02:32, Richard Stallman <rms@gnu.org> wrote:
>> scratch/igc doesn't seem to be a very clear name for ode to work with the MPS
>> garbage collectr. While it is still not installed, is this a good time
>> to rename it to the "MPS gc branch"?
>
> I don't have a strong preference, but I think I'd prefer it if
> extensions to the GC interface that might be useful for other GC
> implementations (and that's most of the changes outside of "igc.c")
> used plain gc_ prefixes. So my proposal would be to rename the branch
> to scratch/mps-gc (or feature/mps-gc), and try to reduce usage of the
> igc identifier (I believe all "mps" identifiers already are isolated
> to igc.c; perhaps that file should be renamed, too).
>
> Gerd, what do you think?
>
> Pip
I agree and suggest as well feature/mps-gc (or feature/mps_gc). I think
would be more identifiable and as feature branch should get more
visibility and hopefully users testing it.
Bests
Andrea
next prev parent reply other threads:[~2024-07-15 10:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <172010929191.25736.12718952666511242363@vcs2.savannah.gnu.org>
[not found] ` <20240704160812.55782C2BC72@vcs2.savannah.gnu.org>
2024-07-09 12:28 ` scratch/igc 26ea4b462a0: Fix GTK-related MPS crashes Andrea Corallo
2024-07-09 13:58 ` Pip Cet
2024-07-09 14:12 ` Andrea Corallo
2024-07-09 14:16 ` Po Lu
2024-07-09 17:19 ` Pip Cet
2024-07-09 21:11 ` Andrea Corallo
2024-07-11 2:32 ` Richard Stallman
2024-07-13 20:35 ` Pip Cet
2024-07-14 2:49 ` Gerd Möllmann
2024-07-15 10:24 ` Andrea Corallo [this message]
2024-07-24 3:02 ` Stefan Kangas
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=yp1cynfar6e.fsf@fencepost.gnu.org \
--to=acorallo@gnu.org \
--cc=eller.helmut@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=luangruo@yahoo.com \
--cc=pipcet@protonmail.com \
--cc=rms@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).