unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-devel@gnu.org
Subject: Re: Improving representation of EIEIO objects in backtraces/error messages
Date: Fri, 30 Dec 2016 09:45:20 +0200	[thread overview]
Message-ID: <83lguxuagf.fsf@gnu.org> (raw)
In-Reply-To: <87o9zump6w.fsf@ericabrahamsen.net> (message from Eric Abrahamsen on Thu, 29 Dec 2016 12:54:15 -0800)

> From: Eric Abrahamsen <eric@ericabrahamsen.net>
> Date: Thu, 29 Dec 2016 12:54:15 -0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: Eric Abrahamsen <eric@ericabrahamsen.net>
> >> Date: Thu, 29 Dec 2016 11:02:47 -0800
> >> 
> >> Can I open a bug report?
> >
> > Sure, you don't need a permission for that.
> 
> Done, as #25295. Sometimes it seems like a wontfix or early-stage
> responses are better got on emacs-devel, but maybe that's not necessary.

There's nothing wrong with wontfix: the bug is still recorded by the
tracker, and someone, some day could decide to fix it.

Therefore, asking here should not be necessary, but there's nothing
wrong with that, either.

Thanks.



  reply	other threads:[~2016-12-30  7:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-29 19:02 Improving representation of EIEIO objects in backtraces/error messages Eric Abrahamsen
2016-12-29 20:32 ` Eli Zaretskii
2016-12-29 20:54   ` Eric Abrahamsen
2016-12-30  7:45     ` Eli Zaretskii [this message]
2016-12-31 19:48 ` Eric Ludlam
2016-12-31 20:48   ` Eric Abrahamsen
2017-01-08  1:51     ` Eric Ludlam
2017-01-08 17:24       ` Eric Abrahamsen
2017-01-12  0:47         ` Eric Ludlam
2017-01-12  1:36           ` Eric Abrahamsen
2017-01-12  1:47           ` Noam Postavsky

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=83lguxuagf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=eric@ericabrahamsen.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 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).