From: Glenn Morris <rgm@gnu.org>
To: emacs-devel@gnu.org
Cc: "Mattias Engdegård" <mattiase@acm.org>
Subject: Re: master d0c4765: Faster, more compact, and readable closure creation
Date: Sun, 21 Feb 2021 22:06:47 -0500 [thread overview]
Message-ID: <i2lfbgls1k.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <20210221210044.1F98B20B7C@vcs0.savannah.gnu.org> ("Mattias \=\?utf-8\?Q\?Engdeg\=C3\=A5rd\=22's\?\= message of "Sun, 21 Feb 2021 16:00:43 -0500 (EST)")
> branch: master
> commit d0c47652e527397cae96444c881bf60455c763c1
> Faster, more compact, and readable closure creation
Please fix test/lisp/emacs-lisp/cconv-tests.
next parent reply other threads:[~2021-02-22 3:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210221210042.2125.20414@vcs0.savannah.gnu.org>
[not found] ` <20210221210044.1F98B20B7C@vcs0.savannah.gnu.org>
2021-02-22 3:06 ` Glenn Morris [this message]
2021-02-22 10:03 ` master d0c4765: Faster, more compact, and readable closure creation Mattias Engdegård
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=i2lfbgls1k.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mattiase@acm.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).