From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo Newsgroups: gmane.emacs.devel Subject: Re: New "make benchmark" target Date: Tue, 31 Dec 2024 09:34:08 -0500 Message-ID: References: <87h679kftn.fsf@protonmail.com> <87frm51jkr.fsf@protonmail.com> <861pxpp88q.fsf@gnu.org> <87frm5z06l.fsf@protonmail.com> <86msgdnqmv.fsf@gnu.org> <87wmfhxjce.fsf@protonmail.com> <86jzbhnmzg.fsf@gnu.org> <87o70txew4.fsf@protonmail.com> <86frm5nii8.fsf@gnu.org> <87jzbgpkon.fsf@protonmail.com> <86ttakm2t2.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4948"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Pip Cet , stefankangas@gmail.com, mattiase@acm.org, eggert@cs.ucla.edu, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Dec 31 15:34:33 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1tSdKL-00018K-EP for ged-emacs-devel@m.gmane-mx.org; Tue, 31 Dec 2024 15:34:33 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tSdK2-000564-Rp; Tue, 31 Dec 2024 09:34:14 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tSdK1-00055w-79 for emacs-devel@gnu.org; Tue, 31 Dec 2024 09:34:13 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tSdK0-0005d0-3m; Tue, 31 Dec 2024 09:34:12 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:Date:References:In-Reply-To:Subject:To: From; bh=C85UeYGCKYUixGpJtL6xAS5RuT87ZAvsqb+q/mB0rtw=; b=beO54FGt415oIDWGnYwq yo3Z8jTWMvxAosZtye/tPN6ya06Tni9h1gL8h0NCVCR4z6uYrfXc/mXM9Pd7hwHdIgVLlbj0W6HBH NI6GFLqafr0bok8k5Q4H0WZWuXowaVZ28T3U+Q//76qmj9BZhF0oxg0KvrZey+HetDe+vsH3qT67u Vlcqzk9vGWyWke7/kDQi9p4b7Be0BTbnL+koCBjQLkr0uI62JI5RlgWi/CxiF9lL0+saTTSUyBjQ6 /RLeFY6YvfJ8LmZqUIeDzTk5Kh05gkIpEbXNWBt4n0WtjfIV5IWVFt1S7rJOrZtBJQ13vP0xA38/A 6MzYK63ezgfT6A==; Original-Received: from acorallo by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1tSdJy-000087-7T; Tue, 31 Dec 2024 09:34:11 -0500 In-Reply-To: <86ttakm2t2.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 31 Dec 2024 14:53:29 +0200") X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:327515 Archived-At: Eli Zaretskii writes: >> Date: Tue, 31 Dec 2024 04:00:05 +0000 >> From: Pip Cet >> Cc: acorallo@gnu.org, stefankangas@gmail.com, mattiase@acm.org, eggert@cs.ucla.edu, emacs-devel@gnu.org >> >> "Eli Zaretskii" writes: >> >> >> Date: Mon, 30 Dec 2024 17:25:44 +0000 >> >> From: Pip Cet >> >> Cc: acorallo@gnu.org, stefankangas@gmail.com, mattiase@acm.org, eggert@cs.ucla.edu, emacs-devel@gnu.org >> >> >> >> "Eli Zaretskii" writes: >> >> >> >> Top-posted TL;DR: let's call Andrea's code "make elisp-benchmarks" and >> >> include it now? That would preserve the Git history and importantly (to >> >> me) reserve the name for now. >> > >> > Fine by me. >> >> Pushed to scratch/elisp-benchmarks. > > Thanks. > >> Sorry for all the noise; we should really find a way to reduce >> emacs-diffs notifications when many commits are made at once. > > I see no reason: people who subscribe to that list should be prepared > for floods from time to time. > >> This branch: >> >> 1. contains whitespace errors, because it contains the files precisely >> as they are in the elisp-benchmarks repo > > We should probably clean that up, unless Andrea says that those > whitespace are somehow needed. Yep, I guess the best for simplicity is to push changes to elisp-benchmarks and later to merge them into emacs-core. AFAIR it's also the way other packages in a similar situation operates.