From: Eli Zaretskii <eliz@gnu.org>
To: Akib Azmain Turja <akib@disroot.org>
Cc: yantar92@gmail.com, 57197@debbugs.gnu.org
Subject: bug#57197: 28.1.90; Can pure side-effect-free functions use multiple CPUs in Elisp?
Date: Mon, 15 Aug 2022 14:46:38 +0300 [thread overview]
Message-ID: <83czd1iva9.fsf@gnu.org> (raw)
In-Reply-To: <87o7wlon9z.fsf@disroot.org> (bug-gnu-emacs@gnu.org)
> Cc: 57197@debbugs.gnu.org
> Date: Mon, 15 Aug 2022 15:43:04 +0600
> From: Akib Azmain Turja via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> >> This looks like a feature request, I think emacs-devel is good for that.
> >
> > I have heard on emacs-devel that M-x report-emacs-bug should also be
> > used for feature requests. Moreover, CONTRIBUTE says:
> >
> > Bug reports and fixes, feature requests and patches/implementations
> > should be sent to bug-gnu-emacs@gnu.org, the bug/feature list. This
> > is coupled to the https://debbugs.gnu.org tracker. It is best to use
> > the command 'M-x report-emacs-bug RET' to report issues to the tracker
> > (described below). Be prepared to receive comments and requests for
> > changes in your patches, following your submission.
> >
> > Let me know if I miss something.
>
> Maybe I'm wrong. But looks like discussion takes place mainly on
> emacs-devel. Please correct me if I'm wrong.
You are both right.
Feature requests should in general be sent as bug reports. However,
if a feature request is likely to mean a major redesign of a large
part of Emacs, it is best first to discuss it on emacs-devel, so that
we could assess its feasibility with more hands on deck.
prev parent reply other threads:[~2022-08-15 11:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 4:18 bug#57197: 28.1.90; Can pure side-effect-free functions use multiple CPUs in Elisp? Ihor Radchenko
2022-08-15 5:57 ` Akib Azmain Turja
2022-08-15 7:13 ` Lars Ingebrigtsen
2022-08-15 8:05 ` Ihor Radchenko
2022-08-15 9:43 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-15 11:46 ` Eli Zaretskii [this message]
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=83czd1iva9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57197@debbugs.gnu.org \
--cc=akib@disroot.org \
--cc=yantar92@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).