From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Andrea Corallo <akrl@sdf.org>, emacs-devel@gnu.org
Subject: Re: [ELPA] New package: elisp-benchmarks
Date: Sat, 07 Dec 2019 13:03:52 -0800 [thread overview]
Message-ID: <87wob726h3.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <jwvh82c0z8x.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 07 Dec 2019 13:27:11 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Is the expectation that we'd actually be committing benchmarks to the
>> benchmarks package?
>
> I think so, yes.
>
>> Both approaches seem a bit awkward -- for the former, you'd
>> have to update the benchmark package whenever any other package updated
>> its benchmarks.
>
> Not sure what you mean by "other package". AFAIK this is meant as
> a benchmark of Elisp itself, so it shouldn't depend on anything
> else than Emacs and shouldn't be affected by changes in third
> party packages.
Oh, I thought this was a general facility that other ELPA packages were
supposed to be able to use, as well. If it's only for Elisp, maybe it
could just go into core?
next prev parent reply other threads:[~2019-12-07 21:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 19:06 [ELPA] New package: elisp-benckmarks Andrea Corallo
2019-12-05 19:18 ` [ELPA] New package: elisp-benchmarks Andrea Corallo
2019-12-06 14:48 ` Andrea Corallo
2019-12-06 19:28 ` Eric Abrahamsen
2019-12-06 22:56 ` Andrea Corallo
2019-12-07 17:27 ` Eric Abrahamsen
2019-12-07 18:27 ` Stefan Monnier
2019-12-07 21:03 ` Eric Abrahamsen [this message]
2019-12-08 0:20 ` Stefan Monnier
2019-12-08 17:15 ` Eric Abrahamsen
2019-12-08 20:38 ` Andrea Corallo
2019-12-08 21:05 ` Eric Abrahamsen
2019-12-11 11:17 ` Andrea Corallo
2019-12-18 13:13 ` Andrea Corallo
2019-12-19 4:27 ` Stefan Monnier
2019-12-19 8:42 ` Andrea Corallo
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wob726h3.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=akrl@sdf.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.