From: Eli Zaretskii <eliz@gnu.org>
To: Radon Rosborough <radon.neon@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Only signal package.el warnings when needed
Date: Tue, 15 Jan 2019 19:18:51 +0200 [thread overview]
Message-ID: <8336ptet50.fsf@gnu.org> (raw)
In-Reply-To: <CADB4rJHiw0-7xEkwg_arOo11t_-sp9tf7Xx_29-ojkMyi3Ur1A@mail.gmail.com> (message from Radon Rosborough on Mon, 14 Jan 2019 14:46:16 -0700)
> From: Radon Rosborough <radon.neon@gmail.com>
> Date: Mon, 14 Jan 2019 14:46:16 -0700
> Cc: emacs-devel <emacs-devel@gnu.org>
>
> You're right that we have not heard too much about it. However, I
> expect that we will hear a lot more about it if we release Emacs 27
> with the current code. This is because people who run Emacs from HEAD
> are more likely to be advanced users who know how to proceed when
> confronted with a warning message like this.
I'm saying that we should hear the complaints first and devise the
solution only after that. It is quite likely that the actual
complaints will tell us something which will affect the solution we
devise.
> I don't see any downside to installing the patch, but I do see a clear
> benefit to many users. Let me know your thoughts.
Increasing complexity is definitely a downside, at least in my book.
Any complex solution runs the risk of having unintended consequences,
so IMO we should understand the problem better before we decide on a
solution.
next prev parent reply other threads:[~2019-01-15 17:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 4:17 [PATCH] Only signal package.el warnings when needed Radon Rosborough
2019-01-14 15:48 ` Eli Zaretskii
2019-01-14 16:10 ` Robert Pluim
2019-01-14 16:39 ` Eli Zaretskii
2019-01-14 16:48 ` Robert Pluim
2019-01-14 20:14 ` Stefan Monnier
2019-01-14 21:46 ` Radon Rosborough
2019-01-14 21:46 ` Radon Rosborough
2019-01-15 17:18 ` Eli Zaretskii [this message]
2019-01-15 18:43 ` Radon Rosborough
2019-01-15 19:26 ` Eli Zaretskii
2019-01-21 22:45 ` Radon Rosborough
2019-01-22 17:29 ` Eli Zaretskii
2019-01-23 4:06 ` Radon Rosborough
2019-01-23 15:34 ` Eli Zaretskii
2019-01-23 16:00 ` Stefan Monnier
2019-01-23 17:28 ` Radon Rosborough
2019-01-14 22:13 ` Óscar Fuentes
2019-01-14 22:59 ` Clément Pit-Claudel
2019-01-15 10:39 ` João Távora
2019-01-15 17:15 ` Eli Zaretskii
2019-01-15 17:24 ` João Távora
2019-01-14 19:55 ` Stefan Monnier
2019-01-14 20:19 ` Stefan Monnier
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=8336ptet50.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=radon.neon@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).