From: "Gregg Sangster" <gregg@thesangsters.ca>
To: "Christine Lemmer-Webber" <cwebber@dustycloud.org>
Cc: guile-devel@gnu.org
Subject: Re: Guile 3 and wip-elisp/Emacs
Date: Wed, 20 Oct 2021 12:43:51 +0200 [thread overview]
Message-ID: <47-616ff300-3-59b80500@71357260> (raw)
In-Reply-To: <875yts7jcp.fsf@dustycloud.org>
Hi Christine,
Thanks for looking at this! I just noticed that my email address as the committer on 1ba3d7854cac0524f80d3c6113da770505c9eda9 is incorrect. Before merging, can you please change it to gregg@thesangsters.ca?
On Tuesday, October 19, 2021 17:59 EDT, Christine Lemmer-Webber <cwebber@dustycloud.org> wrote:
> I've pushed this as origin/wip-elisp-rebased. I actually rebased it
> again, making some naming adjustments for myself and a couple of
> adjustments having talked to Robin.
>
> If nobody objects, I'd like to merge this into main. Maintainers, if
> you have any objections, speak now or forever hold these commits!
>
> Christine Lemmer-Webber <cwebber@dustycloud.org> writes:
>
> > This is awesome.
> >
> > So, what's stopping us from merging this into guile main now before it
> > bitrots again? :)
> >
> > "Gregg Sangster" <gregg@thesangsters.ca> writes:
> >
> >> Hi Ricardo,
> >>
> >> Thanks, your changes fixed a couple of the test errors I saw.
> >>
> >> On Monday, September 13, 2021 06:56 EDT, Ricardo Wurmus <rekado@elephly.net> wrote:
> >>
> >>>
> >>> Hi Gregg,
> >>>
> >>> > I've rebased the wip-elisp branch on top of commit
> >>> > 449f50dd84a081aea16ef678e32bf37abe429ff6 (git describe:
> >>> > v3.0.4-64-g33232cb5c4). It's published here:
> >>> >
> >>> > https://git.sr.ht/~g20r/guile
> >>>
> >>> FWIW I had also rebased wip-elisp in 2020:
> >>>
> >>> https://git.elephly.net/?p=software/guile.git;a=shortlog;h=refs/heads/wip-elisp
> >>>
> >>> --
> >>> Ricardo
> >>>
>
next prev parent reply other threads:[~2021-10-20 10:43 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
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 [this message]
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-616ff300-3-59b80500@71357260 \
--to=gregg@thesangsters.ca \
--cc=cwebber@dustycloud.org \
--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).