From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: philipk@posteo.net, 58950@debbugs.gnu.org
Subject: bug#58950: [PATCH] * lisp/subr.el (buffer-match-p): Optimise performance
Date: Thu, 05 Jan 2023 08:32:15 +0200 [thread overview]
Message-ID: <83k021xzio.fsf@gnu.org> (raw)
In-Reply-To: <9614ebe2-4cf1-30d9-55d2-71a0488f0c2e@yandex.ru> (message from Dmitry Gutov on Thu, 5 Jan 2023 02:02:06 +0200)
> Cc: 58950@debbugs.gnu.org
> Date: Thu, 5 Jan 2023 02:02:06 +0200
> From: Dmitry Gutov <dgutov@yandex.ru>
>
> On 31/12/2022 15:56, Philip Kaludercic wrote:
> > I'd like to backport the
> > changes from bug#58951 and apply them since they are fixing an actual bug.
>
> Speaking of backporting, though, could you address Eli's last message in
> bug#58951? Also, he seems to have reverted the change in the code, but
> not in the docstring.
I hoped the problem would be fixed very soon after the revert. If
this is not going to happen, please adjust the doc string, or tell me
how to do that.
next prev parent reply other threads:[~2023-01-05 6:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 19:11 bug#58950: [PATCH] * lisp/subr.el (buffer-match-p): Optimise performance Philip Kaludercic
2022-11-04 23:00 ` Philip Kaludercic
2022-11-07 1:04 ` Dmitry Gutov
2022-12-31 13:56 ` Philip Kaludercic
2023-01-05 0:00 ` Dmitry Gutov
2023-01-05 4:31 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-05 10:31 ` Mattias Engdegård
2023-01-05 12:55 ` Dmitry Gutov
2023-01-06 11:17 ` Mattias Engdegård
2023-01-06 21:41 ` Dmitry Gutov
2023-01-07 12:57 ` Mattias Engdegård
2023-01-08 21:48 ` Dmitry Gutov
2023-01-09 6:24 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-05 13:01 ` Dmitry Gutov
2023-01-05 0:02 ` Dmitry Gutov
2023-01-05 6:32 ` Eli Zaretskii [this message]
2023-01-05 12:49 ` Dmitry Gutov
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=83k021xzio.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58950@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=philipk@posteo.net \
/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.