unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: MPS experiment successful
Date: Thu, 18 Apr 2024 10:57:29 +0200	[thread overview]
Message-ID: <m2o7a7f3pi.fsf@Pro.fritz.box> (raw)
In-Reply-To: <86ttjzfeb0.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 18 Apr 2024 08:08:35 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>> Cc: emacs-devel@gnu.org
>> Date: Wed, 17 Apr 2024 21:51:07 +0200
>> 
>> I branched cl-packages from master a longer while ago, on Github. That
>> branch has the packages stuff, and I merged master into it once in a
>> while.
>> 
>> Then I branched the igc branch from cl-packages, so it has both the
>> package stuff and the MPS stuff. And I think I merged cl-packages into
>> igc once or twice.
>
> If you have a special branch for MPS, then the diffs from the point
> you forked that branch is all you need.

Ok, there should now be a new branch scratch/igc containing the result
of my attempt to transfer the changes to master.

The branch builds for me without MPS. It cannot possibly compile with
MPS because that part uses CL packages, lacks support for obarrays etc.

The transfer was not entirely easy, and it's likely that I broke
something, even in the non-MPS case.

If someone has the time, it would be helpful to check that this is not
the case. I'm currently too ruthless to do that. Good candidates are
sort.c, fns.c, alloc.c, lisp.h.



  reply	other threads:[~2024-04-18  8:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-17 10:46 MPS experiment successful Gerd Möllmann
2024-04-17 12:22 ` Björn Bidar
     [not found] ` <87cyqo89gk.fsf@>
2024-04-17 12:35   ` Björn Bidar
2024-04-17 13:09 ` Eli Zaretskii
2024-04-17 14:30   ` Gerd Möllmann
2024-04-17 15:49     ` Eli Zaretskii
2024-04-17 16:29       ` Gerd Möllmann
2024-04-17 17:51         ` Eli Zaretskii
2024-04-17 18:34           ` Gerd Möllmann
2024-04-17 19:21             ` Eli Zaretskii
2024-04-17 18:41       ` Gerd Möllmann
2024-04-17 19:23         ` Eli Zaretskii
2024-04-17 19:51           ` Gerd Möllmann
2024-04-17 23:45             ` Dmitry Gutov
2024-04-18  4:27               ` Gerd Möllmann
2024-04-18  5:08             ` Eli Zaretskii
2024-04-18  8:57               ` Gerd Möllmann [this message]
2024-04-18 19:18                 ` Gerd Möllmann
2024-04-17 23:48     ` Dmitry Gutov
2024-04-18  4:31       ` Gerd Möllmann
2024-04-18  9:14     ` Andrea Corallo
     [not found] ` <661fbf1d.050a0220.936ef.ee84SMTPIN_ADDED_BROKEN@mx.google.com>
2024-04-17 13:26   ` Gerd Möllmann
     [not found] ` <661fc22e.170a0220.18fe3.c635SMTPIN_ADDED_BROKEN@mx.google.com>
2024-04-17 13:33   ` Gerd Möllmann
2024-04-17 14:22     ` Björn Bidar
     [not found]     ` <661fdb15.5d0a0220.4bfec.1ac8SMTPIN_ADDED_BROKEN@mx.google.com>
2024-04-17 14:34       ` Gerd Möllmann

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=m2o7a7f3pi.fsf@Pro.fritz.box \
    --to=gerd.moellmann@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).