From: Pip Cet via "Emacs development discussions." <emacs-devel@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: acorallo@gnu.org, stefankangas@gmail.com, mattiase@acm.org,
eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: New "make benchmark" target
Date: Sun, 05 Jan 2025 10:18:02 +0000 [thread overview]
Message-ID: <87jzb9d0q3.fsf@protonmail.com> (raw)
In-Reply-To: <86r05ibfaa.fsf@gnu.org>
"Eli Zaretskii" <eliz@gnu.org> writes:
>> I'm happy to change the scratch/elisp-benchmarks branch in the ways
>> we've discussed, and it should be merged, but if someone decides to
>> incrementally solve some of the issues, that, while not very harmful,
>> would be an inefficient use of resources.
>
> Let's hear what Andrea thinks about the issues you reported (let's
> please discuss them on the bug tracker, not here), and let's take it
> from there.
Sure, just let me know when we can merge the branch (assuming you meant
to say that the merge, too, should wait for Andrea's thoughts) or which
other changes are required!
Pip
next prev parent reply other threads:[~2025-01-05 10:18 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 22:37 Improving EQ Pip Cet via Emacs development discussions.
2024-12-12 6:36 ` Eli Zaretskii
2024-12-12 8:23 ` Andrea Corallo
2024-12-12 8:36 ` Pip Cet via Emacs development discussions.
2024-12-12 9:18 ` Eli Zaretskii
2024-12-12 9:35 ` Visuwesh
2024-12-12 10:40 ` Andrea Corallo
2024-12-12 17:46 ` Pip Cet via Emacs development discussions.
2024-12-12 19:09 ` Eli Zaretskii
2024-12-12 10:53 ` New "make benchmark" target Stefan Kangas
2024-12-12 10:59 ` Andrea Corallo
2024-12-12 16:53 ` Pip Cet via Emacs development discussions.
2024-12-13 0:49 ` Stefan Kangas
2024-12-13 7:37 ` Andrea Corallo
2024-12-14 12:00 ` Stefan Kangas
2024-12-14 14:06 ` Stefan Monnier
2024-12-14 11:34 ` Pip Cet via Emacs development discussions.
2024-12-14 11:58 ` Stefan Kangas
2024-12-14 20:07 ` Pip Cet via Emacs development discussions.
2024-12-14 20:20 ` João Távora
2024-12-15 0:57 ` Stefan Kangas
2024-12-22 16:04 ` Pip Cet via Emacs development discussions.
2024-12-29 10:47 ` Andrea Corallo
2024-12-30 11:45 ` Pip Cet via Emacs development discussions.
2024-12-30 14:15 ` Eli Zaretskii
2024-12-30 15:00 ` Pip Cet via Emacs development discussions.
2024-12-30 15:21 ` Eli Zaretskii
2024-12-30 15:49 ` Pip Cet via Emacs development discussions.
2024-12-30 15:53 ` João Távora
2024-12-30 16:40 ` Eli Zaretskii
2024-12-30 17:25 ` Pip Cet via Emacs development discussions.
2024-12-30 18:16 ` Eli Zaretskii
2024-12-31 4:00 ` Pip Cet via Emacs development discussions.
2024-12-31 5:26 ` Stefan Kangas
2024-12-31 13:05 ` Eli Zaretskii
2024-12-31 14:14 ` Pip Cet via Emacs development discussions.
2024-12-31 14:22 ` Eli Zaretskii
2024-12-31 12:53 ` Eli Zaretskii
2024-12-31 14:34 ` Andrea Corallo
2024-12-30 18:26 ` Andrea Corallo
2024-12-30 18:58 ` Stefan Kangas
2024-12-30 21:34 ` Pip Cet via Emacs development discussions.
2024-12-31 9:55 ` Andrea Corallo
2024-12-31 12:43 ` Eli Zaretskii
2024-12-31 14:01 ` Pip Cet via Emacs development discussions.
2025-01-04 16:34 ` Pip Cet via Emacs development discussions.
2025-01-04 18:33 ` Eli Zaretskii
2025-01-05 10:18 ` Pip Cet via Emacs development discussions. [this message]
2025-01-06 11:23 ` Andrea Corallo
2025-01-06 14:46 ` Eli Zaretskii
2025-01-06 18:41 ` Andrea Corallo
2024-12-15 0:58 ` Stefan Kangas
2024-12-12 10:42 ` Improving EQ Óscar Fuentes
2024-12-12 10:50 ` Andrea Corallo
2024-12-12 11:21 ` Óscar Fuentes
2024-12-13 12:24 ` Pip Cet via Emacs development discussions.
2024-12-12 17:05 ` Pip Cet via Emacs development discussions.
2024-12-12 18:10 ` John ff
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=87jzb9d0q3.fsf@protonmail.com \
--to=emacs-devel@gnu.org \
--cc=acorallo@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=mattiase@acm.org \
--cc=pipcet@protonmail.com \
--cc=stefankangas@gmail.com \
/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).