From: "Gregg Sangster" <gregg@thesangsters.ca>
To: "Ricardo Wurmus" <rekado@elephly.net>
Cc: "Christine Lemmer-Webber" <cwebber@dustycloud.org>,
"Dr. Arne Babenhauserheide" <arne_bab@web.de>,
guile-devel@gnu.org
Subject: Re: Guile 3 and wip-elisp/Emacs
Date: Wed, 20 Oct 2021 12:56:59 +0200 [thread overview]
Message-ID: <47-616ff600-b-59b80500@71357392> (raw)
In-Reply-To: <87bl3rtsiq.fsf@elephly.net>
Hi Ricardo,
On Thursday, October 14, 2021 13:34 EDT, Ricardo Wurmus <rekado@elephly.net> wrote:
> I also had he same experience. Guile Emacs would segfault very
> quickly. That’s why I started a rebase on top of the nearest
> Emacs release, which is 25.2. I had to abandon the rebase,
> because after about 45 commits it became too difficult for me to
> understand what exactly I had to do to resolve all these
> conflicts. There are about 112 commits left to apply.
>
> If you think you could benefit from the work I already did I could
> upload the full git repo as it is, mid-rebase and all.
If you'd like to upload it, I think it would be a great reference.
I've taken the strategy of rebasing forwards along the master branch a few commits at a time. So far I'm about a thousand commits ahead. It's time consuming but the conflicts to resolve are smaller. There are just more of them. :)
--
Gregg
next prev parent reply other threads:[~2021-10-20 10:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 15:12 Guile 3 and wip-elisp/Emacs Gregg Sangster
2021-09-10 19:59 ` Dr. Arne Babenhauserheide
2021-09-13 2:13 ` Christine Lemmer-Webber
2021-10-14 14:01 ` Gregg Sangster
2021-10-14 17:34 ` Ricardo Wurmus
2021-10-20 10:56 ` Gregg Sangster [this message]
2021-10-21 14:05 ` Ricardo Wurmus
2021-10-21 17:49 ` Robin Templeton
2021-10-20 11:59 ` Robin Templeton
2021-09-13 10:56 ` Ricardo Wurmus
2021-09-20 10:39 ` Gerry Agbobada
2021-10-14 13:35 ` Gregg Sangster
2021-10-16 5:25 ` Christine Lemmer-Webber
2021-10-19 21:59 ` Christine Lemmer-Webber
2021-10-19 22:29 ` Ludovic Courtès
2021-10-20 1:46 ` Christine Lemmer-Webber
2021-10-20 2:51 ` Christine Lemmer-Webber
2021-10-20 16:27 ` Christopher Allan Webber
2021-10-22 16:11 ` Christine Lemmer-Webber
2021-10-22 16:17 ` Christine Lemmer-Webber
2021-10-22 18:38 ` Gregg Sangster
2021-10-21 19:34 ` Robin Templeton
2021-10-22 2:59 ` Christine Lemmer-Webber
2021-10-20 10:43 ` Gregg Sangster
2021-10-20 11:43 ` Robin Templeton
-- strict thread matches above, loose matches on Subject: below --
2021-09-10 15:09 Gregg Sangster
2021-09-10 15:09 Gregg Sangster
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=47-616ff600-b-59b80500@71357392 \
--to=gregg@thesangsters.ca \
--cc=arne_bab@web.de \
--cc=cwebber@dustycloud.org \
--cc=guile-devel@gnu.org \
--cc=rekado@elephly.net \
/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).