From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 14786@debbugs.gnu.org
Subject: bug#14786: 24.3.50; `field-end' is now very slow
Date: Fri, 05 Jul 2013 21:33:49 +0300 [thread overview]
Message-ID: <83zju0yhyq.fsf@gnu.org> (raw)
In-Reply-To: <e5457a6f-1e4f-4717-ac71-124a102c74db@default>
> Date: Fri, 5 Jul 2013 10:06:41 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 14786@debbugs.gnu.org
>
> For my info: When such a code change is made, is there no log of the
> reason behind the change?
Every change comes with a change log. The reason is not always stated
in the change log, it can sometimes be in the comments to the changed
code or in some discussion that led to the change (preferably cited in
the change log).
> If it was to fix a bug, for instance, wouldn't that bug # be noted?
Yes, definitely.
next prev parent reply other threads:[~2013-07-05 18:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<029969a6-cd0e-45c9-b778-57b5daf98c2a@default>
[not found] ` <<8338rtyp0y.fsf@gnu.org>
2013-07-05 17:06 ` bug#14786: 24.3.50; `field-end' is now very slow Drew Adams
2013-07-05 18:33 ` Eli Zaretskii [this message]
[not found] <<82afc751-3de7-4315-833d-fa6c9ab9378a@default>
[not found] ` <<83sizuz791.fsf@gnu.org>
2013-07-04 20:57 ` Drew Adams
2013-07-05 16:01 ` Eli Zaretskii
2021-12-04 3:45 ` Lars Ingebrigtsen
2013-07-04 5:34 Drew Adams
2013-07-04 15:15 ` Eli Zaretskii
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=83zju0yhyq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=14786@debbugs.gnu.org \
--cc=drew.adams@oracle.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).