From: Drew Adams <drew.adams@oracle.com>
To: Xavier Maillard <xavier@maillard.im>, help-gnu-emacs@gnu.org
Subject: RE: Elpa: report a bug
Date: Mon, 11 Feb 2019 21:03:50 -0800 (PST) [thread overview]
Message-ID: <7bfed029-19a5-46d8-b0d4-5d48f339f035@default> (raw)
In-Reply-To: <<E1gtPtK-0003vR-Pz@eggs.gnu.org>>
> I am subscribed to the gnu-emacs-source ML and, as such, I receive
> every Elpa updates. So far so good except one (big) thing: the update
> message is useless and laconic.
>
> It just says something like: a new version is here, get it there
> (resume).
>
> There are no mention of what has changed or what the package does.
+1.
> Where should I report this /bug/ exactly?
Dunno. emacs-devel@gnu.org? `M-x report-emacs-bug'?
Perhaps someone will suggest something more appropriate.
next parent reply other threads:[~2019-02-12 5:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<E1gtPtK-0003vR-Pz@eggs.gnu.org>
2019-02-12 5:03 ` Drew Adams [this message]
2019-02-12 4:41 Elpa: report a bug Xavier Maillard
2019-02-12 14:47 ` 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=7bfed029-19a5-46d8-b0d4-5d48f339f035@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=xavier@maillard.im \
/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.
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).