From: Howard Melman <hmelman@gmail.com>
To: 74604@debbugs.gnu.org
Subject: bug#74604: 30.0.92; FR: M-x package-upgrade - offer an option to show a diff on upgrade
Date: Thu, 05 Dec 2024 17:42:08 -0500 [thread overview]
Message-ID: <ly4j3hlpkv.fsf@gmail.com> (raw)
In-Reply-To: <87h67quk0g.fsf@daniel-mendler.de>
Daniel Mendler via "Bug reports for GNU Emacs, the Swiss
army knife of text editors" <bug-gnu-emacs@gnu.org> writes:
> Ship Mints <shipmints@gmail.com> writes:
>
>> To help determine the value/risk of a
>> package install or update, I'd think it better to show this in advance.
>> Daniel's diff suggestion is similar but more technical.
>
> I think your idea of adding an option to show the change log is good. It
> would be nice to have a `package-upgrade-review' option which could be
> set to `nil', `news' or to `diff'.
There was a package called paradox which had more features
on the package UI. It included a command
paradox-commit-list that opened a buffer showing one line
per commit with the commit message and a button that was a
link to the commits diff. It bolded the commits since the
current installed version to make it easy to see the
changes. It only worked on github hosted packages. It
would be great to have this functionality in package.el
particularly if it worked on non-github hosted packages.
--
Howard
next prev parent reply other threads:[~2024-12-05 22:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 15:39 bug#74604: 30.0.92; FR: M-x package-upgrade - offer an option to show a diff on upgrade Daniel Mendler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-01 22:05 ` Philip Kaludercic
2024-12-01 22:47 ` Ship Mints
2024-12-02 8:59 ` Philip Kaludercic
2024-12-02 12:04 ` Ship Mints
2024-12-02 12:18 ` Philip Kaludercic
2024-12-02 12:25 ` Daniel Mendler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-05 22:42 ` Howard Melman [this message]
2024-12-01 23:12 ` Daniel Mendler via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=ly4j3hlpkv.fsf@gmail.com \
--to=hmelman@gmail.com \
--cc=74604@debbugs.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).