From: Ricardo Wurmus <rekado@elephly.net>
To: guile-devel@gnu.org
Subject: rebased wip-elisp
Date: Tue, 16 Jun 2020 23:52:01 +0200 [thread overview]
Message-ID: <87sgeuu1a6.fsf@elephly.net> (raw)
Hi,
I rebased the wip-elisp branch on top of upstream/stable-2.2 and
published it here:
https://git.elephly.net/?p=software/guile.git;a=shortlog;h=refs/heads/wip-elisp
I had to resolve a few minor conflicts and added two commits on top to
fix things that had broken due to changes in the API. “make check”
passes now, but I should also say that Guile Emacs built with this
variant of Guile segfaults.
--
Ricardo
next reply other threads:[~2020-06-16 21:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 21:52 Ricardo Wurmus [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-28 19:00 rebased wip-elisp Gerry Agbobada
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sgeuu1a6.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guile-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.
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).