From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 67483-done@debbugs.gnu.org, acm@muc.de
Subject: bug#67483: Wrong warning position given by the byte compiler for a malformed function
Date: Mon, 27 Nov 2023 15:47:47 +0000 [thread overview]
Message-ID: <ZWS6I_CldqvHTQPk@ACM> (raw)
In-Reply-To: <83r0kb8c89.fsf@gnu.org>
Hello, Eli.
On Mon, Nov 27, 2023 at 17:09:10 +0200, Eli Zaretskii wrote:
> > Date: Mon, 27 Nov 2023 14:01:40 +0000
> > Cc: 67483@debbugs.gnu.org, acm@muc.de
> > From: Alan Mackenzie <acm@muc.de>
> > > > > Which branch? master or emacs-29?
> > > > Both. Probably emacs-28, too.
> > > So it isn't a "semi-recent" problem, is it?
> > It isn't ten years old, either. I have a fix ready to commit to the
> > master branch.
> > Seeing as how the bug isn't recently introduced, and isn't a critical
> > bug, I'm assuming the patch is not destined for the release branch.
> Definitely not.
No. I've committed the fix to master, and I'm closing the bug.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2023-11-27 15:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 12:40 bug#67483: Wrong warning position given by the byte compiler for a malformed function Alan Mackenzie
2023-11-27 13:14 ` Eli Zaretskii
2023-11-27 13:20 ` Alan Mackenzie
2023-11-27 13:50 ` Eli Zaretskii
2023-11-27 14:01 ` Alan Mackenzie
2023-11-27 15:09 ` Eli Zaretskii
2023-11-27 15:47 ` Alan Mackenzie [this message]
2023-11-30 10:37 ` Mattias Engdegård
2023-12-04 18:19 ` Alan Mackenzie
2023-12-19 18:23 ` Mattias Engdegård
2023-12-21 12:22 ` Mattias Engdegård
2023-12-22 11:24 ` Alan Mackenzie
2023-12-22 13:12 ` Mattias Engdegård
2023-12-22 20:09 ` Alan Mackenzie
2024-01-13 14:05 ` Alan Mackenzie
2023-12-04 16:44 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <handler.67483.B.170108887925620.ack@debbugs.gnu.org>
2023-12-08 20:19 ` bug#67483: Acknowledgement (Wrong warning position given by the byte compiler for a malformed function) Alan Mackenzie
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=ZWS6I_CldqvHTQPk@ACM \
--to=acm@muc.de \
--cc=67483-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).