From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: zshaftel@gmail.com, 42499@debbugs.gnu.org
Subject: bug#42499: [PATCH] Add Bytecode Offset information to Backtrace
Date: Sat, 17 Oct 2020 12:32:43 +0300 [thread overview]
Message-ID: <83h7qttcxw.fsf@gnu.org> (raw)
In-Reply-To: <87ft6dusmq.fsf@gnus.org> (message from Lars Ingebrigtsen on Sat, 17 Oct 2020 11:08:29 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Sat, 17 Oct 2020 11:08:29 +0200
> Cc: 42499@debbugs.gnu.org
>
> > If you disassemble one of the annotated functions, you can find the
> > instruction where the error occured.
>
> Sounds useful, but probably somewhat less so since Emacs is moving to
> natively compiling Elisp in Emacs 28. Does anybody else have an opinion
> here?
I don't think we should start dismissing .elc compiled files just
because native compilation is on the horizon. Some users might
legitimately decide they don't want their Lisp natively-compiled, or
may be unable to do so because of the GCC version they have
installed. We should continue supporting byte-compilation features
for the next few versions at least.
> > My copyright assignment is still pending so I assume this can't be
> > merged until I hear back from copyright-clerk.
>
> This was in July, and I can't see your name in the copyright assingment
> file. Did the assignment process stall?
I have an email from Craig in late August saying the disclaimer is
being submitted to legal. Suggest to ping Craig about this.
next prev parent reply other threads:[~2020-10-17 9:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 23:29 bug#42499: [PATCH] Add Bytecode Offset information to Backtrace Zach Shaftel
2020-10-17 9:08 ` Lars Ingebrigtsen
2020-10-17 9:32 ` Eli Zaretskii [this message]
2020-10-18 4:15 ` Richard Stallman
2020-10-18 8:11 ` Lars Ingebrigtsen
2020-10-18 15:03 ` Eli Zaretskii
2021-05-13 9:54 ` Lars Ingebrigtsen
2021-05-13 10:25 ` Eli Zaretskii
2021-06-12 12:14 ` Lars Ingebrigtsen
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=83h7qttcxw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=42499@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=zshaftel@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).