From: Chong Yidong <cyd@stupidchicken.com>
To: Phil Hagelberg <phil@hagelb.org>
Cc: Donald Curtis <dcurtis@gmail.com>, emacs-devel@gnu.org
Subject: Re: First attempt at package-update-all for package.el
Date: Wed, 14 Sep 2011 22:14:12 -0400 [thread overview]
Message-ID: <87fwjyo8ln.fsf@stupidchicken.com> (raw)
In-Reply-To: <87aaa6sxbj.fsf@stupidchicken.com> (Chong Yidong's message of "Wed, 14 Sep 2011 16:06:40 -0400")
Chong Yidong <cyd@stupidchicken.com> writes:
> Phil Hagelberg <phil@hagelb.org> writes:
>
>> For the record, this is a commonly-requested feature where people ask
>> "why doesn't it do this?" and the response is generally "I dunno, but
>> it shouldn't be hard to implement; why don't you try?" =)
>>
>> Would be great to get this in once the feature freeze has melted.
>> What's the procedure for handling patches in this situation? Just ask
>> the author to re-submit after the release?
>
> I've discussed with Stefan, and we agree that it's important to have
> something like this in 24.1. I'll take care of it shortly.
OK, I've committed a package-menu-mark-upgrades command to the Package
Menu, bound to U. This places the appropriate flags for upgrading
packages that can be upgraded. M-x list-packages also issues a message
if any packages can be upgraded.
As for a M-x package-upgrade-all command, I'm not sure yet. The code
written by OP is on the right track, but it also needs some additional
machinery for displaying what packages are going to be upgraded
(possibly using a Package Menu buffer?) and prompting the user.
prev parent reply other threads:[~2011-09-15 2:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 16:32 First attempt at package-update-all for package.el Donald Curtis
2011-09-14 19:05 ` Phil Hagelberg
2011-09-14 20:06 ` Chong Yidong
2011-09-15 2:14 ` Chong Yidong [this message]
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=87fwjyo8ln.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=dcurtis@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=phil@hagelb.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).